Hi Louis,
> I have found what appears to be a memory leak. It happens when you do
> a series of captures in the multidimensional mode and then either abort that
> or allow it to finish and then say you do not wish to save the captured
> frames. This shows up because we are testing an interface and must do many
> of these capture series but do not wish to save them. What happens is that
> windows will eventually become unresponsive and you it will cease to paint
> MM Dialogs on the screen. You can watch the memory in the task manager and
> see it is not released following the aborted capture and save. This is all
> much more pronounced and fails sooner, of course if your image size is
> large.
There is indeed a memory leak in the latest builds of Micro-Manager. We have battled these leaks quite regularly in the past. They are almost always due to UI elements keeping references to pixel or metadata where they should not.
Currently, Henry is re-working the UI code involving the histogram, metadata-panels and drawing of the images. He has already dramatically improved performance. It may be best to wait until he is done refactoring before attacking the memory leaks, since changes to the UI code may easily elicit new leaks. We'll report back here once we have addressed this issue.
Best,
Nico
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Locked
