XnView 1.98.8 memory leak
Posted: Sat Mar 24, 2012 12:53 am
Hello,
recently XnView started bugging me with "out of memory" messages and crashes while browsing and rating images shot with my digital camera. I examined the problem and discovered that repeatedly opening an image in thumbnail view using the "Enter"- key or double-click and switching back to thumbnail view the same way causes XnView to occupy more and more memory until the memory limit for 32-bit programs is reached and the application shows the error message and freezes. I'm running Windows 7 64 bit and deleting the XnView Settings, disabling or enabling thumbnail caching, checking the "No multiple view for same file" setting and updating to the latest version so far did not resolve the problem. The problem seems to be related to image file sizes and strikes faster with bigger files. Another effect of the large memory consumption is an increase in time XnView needs to close the application, the more image switching occurred, the longer it takes to close XnView. Also, while closing, the XnView status bar seems to quickly display every state it ran through during the whole program session in reverse order.
Can anyone reproduce this problem or knows a fix for this?
Thanks,
DeFi
recently XnView started bugging me with "out of memory" messages and crashes while browsing and rating images shot with my digital camera. I examined the problem and discovered that repeatedly opening an image in thumbnail view using the "Enter"- key or double-click and switching back to thumbnail view the same way causes XnView to occupy more and more memory until the memory limit for 32-bit programs is reached and the application shows the error message and freezes. I'm running Windows 7 64 bit and deleting the XnView Settings, disabling or enabling thumbnail caching, checking the "No multiple view for same file" setting and updating to the latest version so far did not resolve the problem. The problem seems to be related to image file sizes and strikes faster with bigger files. Another effect of the large memory consumption is an increase in time XnView needs to close the application, the more image switching occurred, the longer it takes to close XnView. Also, while closing, the XnView status bar seems to quickly display every state it ran through during the whole program session in reverse order.
Can anyone reproduce this problem or knows a fix for this?
Thanks,
DeFi