A new Windows App is available from our Beta Test Page.
It features even more code to track some of the remaining problems. For now we are also distributing the PDB file (containing debugging information) again with the beta package.
This App is the first that has been built with VS2005. I hope that this helps with some of the library problems we see. I don't yet know how this affects the performance.
Please test.
BM
BM

Windows S5R2 App 4.38 available for Beta Test
)
Thanks. Fixed.
BM
BM
No idea what happened, but
)
No idea what happened, but currently it looks like the one I posted (w. Apps 4.37 and 4.38) ...
BM
BM
RE: Interesting: The
)
I am. Actually that output is one of the reasons why I put in some checks that apparently make the App a little slower. Maybe they can be taken out before the next "official" App.
BM
BM
RE: Interesting: The
)
I don't think so.
The other Task ran out of memory (probably was too fragmented). The parameters of result #86540103 (what's following "non-finite Dphi_alpha:"), however, are quite confusing, there's something really weird going on on this computer. There's no way I could see this happening from the source code. Either there's a serious bug in what the compiler makes of it, or some hardware problem on the machine (e.g. bad memory or overheated CPU).
BM
BM
RE: One wingman crashes on
)
It's not different from what I would expect.
The machine that errored out "setting up stacks" clearly has a broken data file (and a Client < 5.6 that doesn't check the files before starting the App).
I wish the other machine had ran the 4.38 App, so I could get a better impression of what's wrong.
It's not an error in the data or the basic algorithm, this '[-8,8]' problem is specific to Windows, probably due to the VC compiler, and to certain machines (and maybe even the current state of the memory there).
I bet you'll find more of the same errors in the result history of both machines.
BM
BM
Though the App is mostly a
)
Though the App is mostly a little slower than the previous one, we decided to push it out official to get some more feedback faster. I hope that it will be superseded by a faster one soon.
We're a bit under pressure now, for S5R3 we are relying on some issues to be fixed in the App.
We also pushed out the Linux App 4.37 to get rid of the "libz" errors.
BM
BM
RE: Don't know how much
)
The "NULL pointer" message doesn't look good. However two machines finished this WU without error, so this doesn't look like a programming error (which the failed sanity check was meant to catch). Watch out for memory problems. Might have some transient problem, thiugh.
BM
BM
RE: This WU could not
)
Sorry, the Wu can't be found anymore. If it had left the active database, it means that a canonical result was found, i.e. at least two machines finished this WU successfully and their results agreed.
There might be something wrong with the URL you gave, though.
BM
BM