No chance of that. I mean you may be able to add in some additional logging options around the suspect processes to see what is happening.
It would also help if others with this issue could confirm the revision where this first appears.
(07-14-2015, 12:36 PM)willkuer Wrote: [ -> ]if it is pr 504 then it is the cso loading function..But I don't know how it could fail on you rig and on everyone else's not except for localization issues (as the cso loader uses file stuff)
The build v1.2.1-504-g05b3301 points to the merge of pr241, where the debugger is now available and enabled on release builds.
(07-15-2015, 05:31 PM)sputnik Wrote: [ -> ]No chance of that. I mean you may be able to add in some additional logging options around the suspect processes to see what is happening.
It would also help if others with this issue could confirm the revision where this first appears.
What version of Windows do you have? I'm guessing Windows 7 64-bit? The other two with the crashing issue seem to have that too.
Could you turn all the logging options on in the console, then make it crash a few times and show where the emulog stops at? It should help narrow things down a bit.
If the emulog stops at the same place each time it crashes then it might be solvable. If not, it's going to be a nightmare to fix.
turtleli: Have you let him test a WX3 build yet? It might be fixed by that or it might provide better error details.