Also, I just had a thought -- maybe doesn't mean too much (LOL) -- but would it be worth while for you (Stephen) to post some of the crashes/problems that you don't have time to get to yet, but maybe some of us can attempt to at least narrow down?
I try to read most of the posts, but really don't have a good feel for the actual "bug list".
Sorry I wish I could provide more information, but I was quickly bouncing around the various views looking to see what was new. If I get any more crashes I will pop it up in the debugger and post the call stack and hopefully the scene that did it. To be honest, having only recently renewing my interest in this app after quite some time away, I wasn't really sure how active you guys are on the development. I'm glad to see you're on top of it and will do what I can to track & provide more information as problems occur. I am hoping to use this as a core content generation tool for a project I am just now starting so I am happy to do what I can to help.
I was testing out 2.3 standard beta 1 and experienced a crash. I wasn't doing anything in particular, just changing views and looking at stuff. As a programmer myself I appreciate how useless my report is to you given how little information there is but that is actually the point of my post - I would like to suggest adding an exception handling mechanism that emails you the call stack and registers when a crash occurs. I have found this to be extremely helpful in dealing with application errors experienced by customers and well worth the effort it takes to implement it. Depending on the situation you could possibly even save a user's work prior to exiting, giving them a chance to recover data (although it could be corrupt) but that could perhaps also provide you with the data you need to reproduce a crash.
Glad to see you are actively working on World Machine again!