Client version 4.56 being released

Message boards : Client : Client version 4.56 being released
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Janus
Volunteer moderator
Project administrator
Avatar

Send message
Joined: 16 Jun 04
Posts: 4574
Credit: 2,100,463
RAC: 8
Message 6824 - Posted: 7 Oct 2007, 21:22:53 UTC
Last modified: 8 Oct 2007, 21:57:00 UTC

This version is released to fix two of the known problems with the current client:
1) When Blender itself crashes it will leave a message-box on Windows machines, informing about the crash. This blocks further progress for a few hours.
This behaviour should now no longer happen, instead the crash is recorded in the resultfile and sent back to the project automatically. The data being sent back does not include any personal information (in fact it only includes the message \"Unhandled segmentation violation\" and the usual result debug text). This bug was recently triggered by session 641.

2) When forcibly aborting (not exiting) any Glue2-connected renderer Glue2 will crash and leave the renderer hanging.
Glue2 should now correctly identify the BOINC abort signal and take appropriate action by killing the Blender process.

The new client also includes Blender code based on Blender version 2.45. Usually we have used SVN/CVS versions of Blender, but this time it has been based on the official tarball available from blender.org.

The client is rolled out during the extended monday maintenance tomorrow afternoon (UTC) and will be available on both Windows and Linux platforms. The binary for Linux will still be dynamically linked, meaning that Linux people will have to manually install the relevant libraries (as per the linux FAQ.
If your platform isn\'t supported you will have to compile the client yourself, please have a look at getting the source code and the FAQ for your platform in the client forum.
ID: 6824 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Achim

Send message
Joined: 17 May 05
Posts: 183
Credit: 2,642,713
RAC: 0
Message 6846 - Posted: 8 Oct 2007, 19:44:32 UTC

Can you please update the front page with the latest Blender supported version?
ID: 6846 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Janus
Volunteer moderator
Project administrator
Avatar

Send message
Joined: 16 Jun 04
Posts: 4574
Credit: 2,100,463
RAC: 8
Message 6855 - Posted: 8 Oct 2007, 21:57:43 UTC

Sure thing, version updated.
ID: 6855 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Fischer-Kerli
Project donor

Send message
Joined: 24 Mar 05
Posts: 70
Credit: 78,553
RAC: 0
Message 6858 - Posted: 9 Oct 2007, 12:12:28 UTC - in response to Message 6824.  
Last modified: 9 Oct 2007, 12:12:54 UTC

The data being sent back does not include any personal information (in fact it only includes the message \"Unhandled segmentation violation\" and the usual result debug text).


Hmm ... the \"usual debug text\" includes a section \"Foreground Window Data\" at the end where the entry \"Window Name\" might be (for example) \"[Browser name] - [title of the site you were visiting the moment the app crashed]\". I can think of two or three web sites you\'d prefer to visit without others knowing. And what about the window name \"[put the name of your favourite application with questionable legality here]\"? I remember asking about privacy issues with the standard debug info on some SETI/SETI Beta message board some time ago and getting no response. Maybe someone has got an opinion here?
ID: 6858 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Janus
Volunteer moderator
Project administrator
Avatar

Send message
Joined: 16 Jun 04
Posts: 4574
Credit: 2,100,463
RAC: 8
Message 6859 - Posted: 9 Oct 2007, 12:24:58 UTC - in response to Message 6858.  
Last modified: 9 Oct 2007, 12:44:20 UTC

Hmm ... the \"usual debug text\" includes a section \"Foreground Window Data\"

Not really, the \"usual debug text\" would be something like this:

boinc_init_diagnostics() completed
boinc_init_options() completed
Basename: projects/burp.boinc.dk/blender_4.5x_windows_intelx86.exe --> blender_4.5x_windows_intelx86.exe
Mapping logical files to physical destinations:
in => ../../projects/burp.boinc.dk/661in0.zip
out.zip => ../../projects/burp.boinc.dk/661in0.zip__ses0000000661_frm0000000089_prt00000.wu_0_0
blender_4.5x_windows_intelx86.exe.zip => ../../projects/burp.boinc.dk/blender_4.5x_windows_intelx86.exe.zip
./windows_zip.exe => ../../projects/burp.boinc.dk/windows_zip.exe
./windows_unzip.exe => ../../projects/burp.boinc.dk/windows_unzip.exe
Decompressing input...
Running ../../projects/burp.boinc.dk/windows_unzip.exe -o ../../projects/burp.boinc.dk/661in0.zip
runcmd(../../projects/burp.boinc.dk/windows_unzip.exe -o ../../projects/burp.boinc.dk/661in0.zip) exitted with exit code 0
Decompressing executable archive...
Running ../../projects/burp.boinc.dk/windows_unzip.exe -o ../../projects/burp.boinc.dk/blender_4.5x_windows_intelx86.exe.zip
runcmd(../../projects/burp.boinc.dk/windows_unzip.exe -o ../../projects/burp.boinc.dk/blender_4.5x_windows_intelx86.exe.zip) exitted with exit code 50

---------------------------
Exception caught: Non-zero exit status in Portability::runcmd()
Status: -3
---------------------------

It is true, however, that errors in glue2 may trigger the BOINC debugger, which in turn may return the information you are talking about if that particular feature is enabled.
It is disabled by default in the registry (CaptureForegroundWindow==0)

// Check the registry to see if we are aloud to capture the foreground
// window data. Many people were concerned about privacy issues.
//
// We\'ll turn it off by default, but keep it around just in case we need
// it.
//

In that case what you will see in the log is something like:
*** Foreground Window Data ***
Window Name :
Window Class :
Window Process ID: 0
Window Thread ID : 0


Maybe someone has got an opinion here?

The ability of users to select their level of privacy is an important aspect of publicly distributed computing.
ID: 6859 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Fischer-Kerli
Project donor

Send message
Joined: 24 Mar 05
Posts: 70
Credit: 78,553
RAC: 0
Message 6861 - Posted: 9 Oct 2007, 13:17:55 UTC

Thanks for your clarification! I didn\'t know about the \"CaptureForegroundWindow\" registry entry, and I can\'t find it in my registry, so I guess that\'s identical to having it set to 0. However, if I interpret this Trac changeset correctly (found at random when running a Google search for CaptureForegroundWindow), this registry value is only used in the 5.8.?? and later BOINC clients. (Run a Google search for \"Foreground Window Data\" and (for instance) \"Internet Explorer\", and you\'ll see what it was like before.) Not your problem, though, and I\'m glad to see the BOINC devs fixed it. Another reason for upgrading your BOINC client.
ID: 6861 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
PovAddict
Avatar

Send message
Joined: 25 Apr 05
Posts: 347
Credit: 4,618
RAC: 0
Message 6873 - Posted: 11 Oct 2007, 2:23:44 UTC - in response to Message 6861.  

However, if I interpret this Trac changeset correctly (found at random when running a Google search for CaptureForegroundWindow), this registry value is only used in the 5.8.?? and later BOINC clients. Not your problem, though, and I\'m glad to see the BOINC devs fixed it. Another reason for upgrading your BOINC client.

Who would have a BOINC client older than 8 months??

If you have 5.8, you should upgrade to 5.10 for a few new features. If you have something older than 5.8, put it in a museum and upgrade. 5.4.11 is ancient by now.
ID: 6873 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Client : Client version 4.56 being released