Windows S5R2 App 4.32 available for Beta Test
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4312
Credit: 250191663
RAC: 35048
23 Jul 2007 15:50:02 UTC
Topic 192991
(moderation:
A new Windows App is available from our Beta Test Page.
Minutes after making the 4.30 App official I saw a Client Error from 4.30 Beta Test tumbling in that allowed to track down a cause for our major Client Error (a General Access Violation that lists "houghmap.c" in the stackdump) and hopefully fix it.
Ideally this problem should not occur anymore with this new 4.32 App. Also some flaw in the cross-platform code of the 4.30 was fixed, which should further improve the x-platform-compatibility.
Please test & report!
BM
BM
Windows S5R2 App 4.32 available for Beta Test
)
Oops - there is a small bug in the App that will rapidly fill stderr. I'll fix that. Please don't use it right now!
BM
BM
Ok, I updated the App on the
)
Ok, I updated the App on the Beta Test Page. Note the new MD5, the version number is unchanged.
BM
BM
RE: Ok, I updated the App
)
Runs fine, looks good!
CU
BRM
I just switched two tasks in
)
I just switched two tasks in progress from the 4.28 beta to the 4.32 beta and all is looking good, running smoothly so far.
And what about error code
)
And what about error code 99?
Crashed result
Has it been fixed as well or is it only strange and rare?It happened during video encoding,no other using.And such error have not happened during encode before.
Hmmm... Offhand it looks
)
Hmmm...
Offhand it looks like the app got unhappy about not getting the memory it thought it had available on the restart after the lost heartbeat.
Alinator
Anyone notice any increase in
)
Anyone notice any increase in CPU temperatures with this version, or is it just dust (less airflow) and that I don't have it as cool as normal here in the room?
RE: And what about error
)
Thank you very much for the report!
Exit code 99 in general means that an internal sanity check failed. Which one is listed in the status dump at the end of stderr_out.
In your case it lists an "out of memory" while reading data files (SFTs). The reason might indeed be too little memory, but since it obviously succeeded previously, that's rather unlikely. The amount of memory it tries to allocate depends on data read from the file, if that information is corrupt, the amount of memory it tries to allocate might be too large. However the Client should now check the consistency (md5 sums) of all data files before starting a task, so a broken file is unlikely, too.
I'll add some code to write out the amount of memory it requested in case the request failed, which should give a better idea of what goes wrong, but that will appear only in the next App version.
BM
BM
One WU particular done with
)
One WU particular done with 4.32, seems to be fine:
http://einsteinathome.org/workunit/34317672
Another WU just half finished, graphics works, too. Just wait wait for finish and validation. The speed seems to be same as 4.30.
Are any speedimprovemnts palnned for future version?
RE: Are any
)
There are. But given the current progress in finding and fixing bugs I'm no longer sure if I'll come to that this week.
BM
BM