[lom109]

So i'm running this program, and it has heavy I/O with the database.

And I'm profiling it, but it stops profiling at the 11 second mark...
(meaning it begins to indicate “bytes/second: 0 & events/second: 0”)

The program however is running as I can see my file being generated in windows explorer.

MY problem is that the program runs indefinitely on profiler mode (meaning after the file is finished, and everything, the timer keeps counting up). On normal run/debug, the program works perfectly as planned and exits > 0.
Additionally, when I attempt to kill the profiler PID, eclipse ignores me until I manually terminate the entire program via Task Manager.

Any idea what could be causing this?
Additional Note: normal run takes about 3 minutes to finish generating the file. Would the time have an adverse affect upon the profiler?