Honda Motorcycles - FireBlades.org banner

1 - 4 of 4 Posts

·
Registered
Joined
·
1,508 Posts
Discussion Starter #1
This is a long shot, but is anyone here a stud with .NET debugging? We have a memory allocation run-time error that is killing us and I need to learn more about how to view the heap during a debug session...
 

·
Registered
Joined
·
96 Posts
ER said:
This is a long shot, but is anyone here a stud with .NET debugging? We have a memory allocation run-time error that is killing us and I need to learn more about how to view the heap during a debug session...
aside from viewing all locals int he default debug screen, i really don't know how to help, as my debugging skills for .net suck...

but i have seen a few webcasts offered by MSDN dealing with debugging in .Net...you might want to check those out...i've found that the webcasts can be very helpful...

good luck!
 

·
Registered
Joined
·
2,047 Posts
ER said:
This is a long shot, but is anyone here a stud with .NET debugging? We have a memory allocation run-time error that is killing us and I need to learn more about how to view the heap during a debug session...
You probably already have, but have you tried Google? It's helped me out a few times when I was in need.....
 

·
Registered
Joined
·
1,508 Posts
Discussion Starter #4 (Edited)
soon2b954 said:
You probably already have, but have you tried Google? It's helped me out a few times when I was in need.....
Yeah, I live on that site. We just had a long meeting and I think we've narrowed it down to a particular module.

For those interested, our product stores scanned images into a DB. We have a client that allows users to take those images and work with them. Since they can upload or download a large number of images at once - and each image can be anywhere from 1KB to 15MB - we have to be careful with how our process uses the Operating System's memory. In this case we are processing requests to the DB asynchronously (which means that data returned is done in a multi-threaded fashion) but our process is not releasing the memory used for those images until each "chunk" is done. So, the process swells to half a GB at times, which exhausts the available virtual memory on the average PC.

PrplHaz4 said:
aside from viewing all locals int he default debug screen, i really don't know how to help, as my debugging skills for .net suck...

but i have seen a few webcasts offered by MSDN dealing with debugging in .Net...you might want to check those out...i've found that the webcasts can be very helpful...

good luck!
I've been on the MSDN site had haven't had too much luck. Same with the .net247 site. :(
 
1 - 4 of 4 Posts
Top