Application fails to close properly then uses all CPU resources

[Guest]

Hi there,

Please excuse this very basic question. I'm an ASP.NET developer and have
never really touched windows forms before.

I've created a little app that loads data from an oracle database using our
DAL and ODP.NET, processes the data and saves it back to the DB. The app
works fine but when a user tries to close the app by clicking the main close
icon the app dissapears from the screen but the process remains in Task
Manager. What's more the it immediately uses up all the available CPU
resources (50% on my two processor machine).

I thought .NET's garbage collector should handle the deconstruction and
clean-up process?

The only things I thought it might be are ODP.NET or StreamWriter that I use
to write a log file with, but I call Close() and Dispose() on the
StreamWriter!

If anyone has any ideas I'd appreciate it.

Thanks

Mat

 

[Michael C]

Hi there,

Please excuse this very basic question. I'm an ASP.NET developer and have
never really touched windows forms before.

I've created a little app that loads data from an oracle database using
our
DAL and ODP.NET, processes the data and saves it back to the DB. The app
works fine but when a user tries to close the app by clicking the main
close
icon the app dissapears from the screen but the process remains in Task
Manager. What's more the it immediately uses up all the available CPU
resources (50% on my two processor machine).

I thought .NET's garbage collector should handle the deconstruction and
clean-up process?

The only things I thought it might be are ODP.NET or StreamWriter that I
use
to write a log file with, but I call Close() and Dispose() on the
StreamWriter!

If anyone has any ideas I'd appreciate it.

Push the pause button in the IDE, it should show you what is currently
executing (assuming it is your code that is executing).

 

[Guest]

Push the pause button in the IDE, it should show you what is currently
executing (assuming it is your code that is executing).

 

[Guest]

Found the problem. It was particular to this app so I won't bother outlining
it here. Thanks for your help.