Forums › TWAIN Classic › application memory and virtual memory increase quickly › Reply To: application memory and virtual memory increase quickly
- Topics - 9
- Replies - 583
- Total Posts - 592
background thoughts, these numbers will be somewhat relative to the memory I have so for reference I’ve got 1Gb allocated to the vmware dev machine running xp sp2 using vs2005 sp1.
I rechecked my native acquisitions and my memory usage does baloon when running from a winforms project, ~400-500Mb peeks memory usage with the app showing around 200Mb in use after I have acquired an image even if i’m not doing anything and as long as that winforms project is the active window (minimize it and it drops to 4Mb, but thats the framework for you). File transfers peek somewhere in the 200-250Mb range with the same memory use when idle after an image has been acquired. Memory usage doesn’t seem to increase with every acquisition, after I take the hit on the first acquisition it’s pretty stable.
the same base library running under a windows service (which btw I’m just tickled with) idles around 20Mb with peek memory usage around 80Mb.
If you put your twain logic in a dll and drive it from a console project that saves the images to a file instead of loadig them to control on a winform, what does your memory usage look like?
also, if you find a solution it’s worth at least a beer to me if you post it to me somehow.