it appears as if your thread is not pumping.
Quote:
Failure to Pump
When your STA thread is doing nothing else, it needs to be checking to see if any other threads want to marshal some calls into it. This is done with a Windows message pump. If the STA thread fails to pump, these incoming calls will be blocked. If the incoming calls are GUI SendMessages or PostMessages (which I think of as synchronous or asynchronous calls respectively), then failure to pump will produce an unresponsive UI. If the incoming calls are COM calls, then failure to pump will result in calls timing out or deadlocking.
If processing one incoming call is going to take a while, it may be necessary to break up that processing with intermittent visits to the message pump. Of course, if you pump you are allowing reentrancy to occur at those points. So the developer loses all his wonderful guarantees of single threading.
|
stolen from:
http://blogs.msdn.com/cbrumme/archiv.../02/66219.aspx
are you doing all of this processing on your main thread? I believe the problem is that your application is being too big of a hog. I have no clue what's in your code so....
as the file gets bigger, however you have it implemented, it should not require any more resources than when working with a small file, it should simply take longer and nothing more, you might want to give it its own thread as well while its churning away. so try that and see what happens.