Guess what? No one here writed^Hwrote it either, and without a sample of the code in question all you're going to get is vague guesses as to what the problem is. Perhaps it's using a module which has a buggy destructor. Perhaps it's trying to surreptitiously upload the entire contents of your drive to flickr. Nobody here knows or could know (the troubles you've seen . . . erhm, sorry). Cut it down to the simplest possible code that exhibits the problem, or at the least give a more detailed outline of what it's doing (modules it's using, descriptions of how it's using them) than the vague one you've given above.

Now having said that, you might try running (OS allowing) something like strace or ktrace and see what system calls it's making under the hood; that may give you a window into what the underlying OS actions it's doing are and point to where the problem lies. But that's just a vague guess.