Flutterby™! : Work...

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics


2004-02-13 22:12:58.386268+00 by Dan Lyke 2 comments

We didn't just track down that bug, we left evidence of its extermination as a warning to other bugs.

[ related topics: Dan's Life Software Engineering ]

comments in ascending chronological order (reverse):

#Comment Re: made: 2004-02-14 16:32:03.235635+00 by: meuon


#Comment Re: made: 2004-02-14 17:44:50.383789+00 by: Dan Lyke

Yep. Not only did we fix the process that was corrupting the file that was causing the third party library to lock up, now any time when we call the third we spawn a separate thread and make sure it doesn't take longer than a few seconds to do what it needs to.

It's probably foolish to depend on the .NET runtime to protect memory in the separate thread, so we should really fork another process, but under Windows that's pretty heavyweight.