- This topic has 4 replies, 4 voices, and was last updated 15 years ago by
.
-
Posts
-
Hi guys!
I believe I’ve finally found the frustratingly die-hard "Child Process Not Responding" bug. The bug seems to have been two mismatched timeouts, so that if the child process took more than 10 seconds to start, it would give up, but at the same time the watchdog code waiting for it would wait 2 whole minutes before realizing that the child process gave up long ago. The solution was simply to make sure both timeouts were 2 minutes. Finding the problem, on the other hand… Not quite so simple.
This has been a major issue with Breakaway — particularly because it often happened when you put the computer to sleep. I sincerely hope this is the last I’ve seen of that particular issue!
Apart from that, I’m setting up a dedicated Windows 7 system as a new development/testbed for Breakaway. Once that’s done, we’re ready for a new release — and it will be a big update this time, with new presets, many issues fixed, and the new FM mode!
Thank you everyone for waiting so patiently.
Best regards,
///LeifWe are patient, as we realize it’s only one person developing this software. I thank YOU for being so thorough and sousing out the odd error here and there, it’s definitely a full time job plus some. Keep up the fantastic work, you always surprise us with your latest and greatest inventions.
Quick question: Will BAE alert us to a new version when it’s released? Or do we need to keep watching the website? Just curious because I didn’t see a "check for update" option anywhere. Thanks for all the hard work! Now that I’ve been using this software for months, it pains me when I’m forced to go without. Great job!
- You must be logged in to reply to this topic.