Windows S5R2 App 4.32 available for Beta Test
23 Jul 2007 15:50:02 UTC
Topic 13573
(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: 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
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
RE: Do you think you can
)
Yep.
My current plan is to use this week to make the code as robust as possible on Windows, which seems by far the most fragile system/App, and then build a new generation of Apps from that code for all platforms that runs as fast as possible.
BM
BM