Menu
▾
▴
#1 JPEGView Crashes
closed
nobody
None
5
2011-03-07
2011-02-20
Anonymous
No
I displayed thirty five images, and when the last image had been displayed the program crashed. The following message was then displayed:
"Runtime Error!
The application has requested the Runtime to terminate in an unusual way."
I am using the application on Windows Xp professional from my desk top, because this free standing product is exactly what I require, and would be grateful if any one would point out what I am doing wrong.
Thanks
John
Is this reproducible? If yes describe the steps to reproduce as exactly as possible. Is it occuring on a specific image?
When you want support mail to jpegview@gmail.com, I do not know your EMail address for direct contact
BR
David
At this time I have identified a single picture that seems to cause the program to crash, I removed this picture, and the program functions normally. However the picture is displayed as it should be and only causes the program to crash when you try to move on to the next picture. I placed this single picture in its own directory and the program displayed this picture normally and did not crash the program. I could not reproduce this problem with any of my other image sets.
I wonder if the picture is causing the program to crash, or whether it is a shortcoming of the program, in any event I do not understand the program code to be able to solve the problem. If it is the picture can any one suggest how to alter the picture so as not to cause a problem?
I take on board your request to email for support, and in future I will comply.
Thanks
John
Is this picture very large and is the next picture to show also very large and/or your total memory of the computer is less than 1 GB?
I am asking because the same error occurs when you try loading extremely large images. Loading one large image alone works more often because JPEGView reads the next image ahead to speed up display of the next image - that's a nice feature but needs a lot of memory.
I know that error handling in low memory situations needs improvement, but the RTL seems to terminate the program in this situation.
The picture is about 79MB and is next to another picture about 78 MB. I Isolated these two pictures and tried displaying them, on a number of occasions the program just crashed as I moved from one to the other, but not before the picture was displayed.. Then the program just started crashing once the initial picture was displayed, in no way did I attempt to move from one picture to the other.
I have about 2GB of physical memory and roughly the same again in virtual memory.
Thanks
John
Can you provide me the size in pixels of these images (e.g. 6000 x 5000 pixels)? This pixel size is more relevant for JPEGView memory usage than the file size.
I could try to turn off read ahead of the next image when a big image is already loaded - this would fix your issue. Better slow in such a case than crash...
The image sizes in pixels are as follows:
1. 6000 x 4501.
2. 9000 x 8886.
Is it possible to manually turn off the read ahead mechanism via a context menu, or a command line switch when the program is initially run.
If turning this read ahead mechanism off solves the problem will you be integrating it into the next release of the program. The reason for asking is that without the ability to turn of the read ahead mechanism in future release I will be forever tied to the present release.
Thanks
John
So it's now clear that its the image size that causes the crash. JPEGView temporarily needs a lot of memory during resizing - with two images that are this large no address space is available anymore in 32 bit.
I will try to turn off read ahead for images that are this large in the next release.
Thanks For All Your Help
John
I have found a solution for this problem - at least I think so.
If you send me your email address to jpegview@gmail.com I can provide you a test version so that you can see if it helps.
David
Improved in 1.0.23