I am using Memory Profiler 2.6 to profile .net 2.0 windows service.
We are doing processing in the service, where if it detects a record in database, it updates it to inprocess from pending and then does lot of work. The service is hogging 1+GB of memory and I am trying to find why its happening.
When I start the service from .net memory profiler, it starts the service, however, it service does not change the record to InProcess from pending (I think its not executing this code, may be its on a different thread? I am just guessing). In general our overall process takes 1to 2 hour to finish, but when used from .net memory profiler, it did not finish it at all, When I tried to take snapshot in between, it hung the app keeping service running and hence I could not take the snapshot. When tried to close app, it asked me to save the session, when I provided the path, it showed a message saying could not save, memory could be corrupted.
if I run the service without memory profiler, everything works as expected (ofcourse with memory loading)
Can you please guide me how to resolve this issue?
You can also reduce the memory consumption of the profiler by enabling low-impact profiling (under the "Interactive" tab in the Tools->Settings dialog).
SciTech Software AB
Users browsing this forum: No registered users and 18 guests