Workflow:
Error message:
"An error occurred. You should save [...]
d:home\muellerm\mitk\src-3m-3_1\mitk\core\code\datamanagement\mitkMemoryUtilities.h:71: Failed to allocate memory."
Hardware:
Laptop Windows XP, 32 bit
Was no real crash, but a freeze up due to the memory being exceeded and constant swapping.
As this is no special problem of the basicimageprocessing, and could only be fixed by monitoring the free memory of the system and either warning a user should he attempt to process an image which in combination with a filter will result in that memory being exceeded or by aborting a filter once the memory is used up, it is not really 3M3 1.1 critical.
Might be of interest for the MITK group. Such a general "Memory might be exceeded" warning could profit MITK as a whole.
Resetting all bugs without active assignee flag to "CONFIRMED". Change status to IN_PROGRESS if you are working on it.
So far there has not been the above mentioned discussion about this. I will put it on my list for the next MITK meeting.
Was diskussed in the MITK meeting:
Since available memory resources and the memory usage of filters cannot be determined generically, there is no universal solution.
Every programmer has to consider the memory usage of his algorithms. If it is excessivly high, the programmer needs to warn the user in his bundle/module.