Version 1.80.3
For the last couple of days I have been working on some very large PNGs... on the order of 100Mb or so. Naturally, saving these files takes a bit of time.
If I inadvertently attempt to close XNView before the file has completed saving (by clicking the main XNView window's close control, for instance...) XNView crashes. Also, since the file hasn't completed saving, it is corrupt.
I also notice that when saving large PNGs XNView does not show an hourglass cursor nor does it show a progress bar. Perhaps if an hourglass showed I would not be so quick to close XNView.
Problem Saving Large Pngs
Moderators: helmut, XnTriq, xnview
Re: Problem Saving Large Pngs
I'll checkJohnFredC wrote:Version 1.80.3
For the last couple of days I have been working on some very large PNGs... on the order of 100Mb or so. Naturally, saving these files takes a bit of time.
If I inadvertently attempt to close XNView before the file has completed saving (by clicking the main XNView window's close control, for instance...) XNView crashes. Also, since the file hasn't completed saving, it is corrupt.
I also notice that when saving large PNGs XNView does not show an hourglass cursor nor does it show a progress bar. Perhaps if an hourglass showed I would not be so quick to close XNView.
Pierre.
Re: Problem Saving Large Pngs
I've checked, and can't reproduce this bug.JohnFredC wrote:Version 1.80.3
For the last couple of days I have been working on some very large PNGs... on the order of 100Mb or so. Naturally, saving these files takes a bit of time.
If I inadvertently attempt to close XNView before the file has completed saving (by clicking the main XNView window's close control, for instance...) XNView crashes. Also, since the file hasn't completed saving, it is corrupt.
I also notice that when saving large PNGs XNView does not show an hourglass cursor nor does it show a progress bar. Perhaps if an hourglass showed I would not be so quick to close XNView.
In view mode, when i save a picture, i have the progress bar, and can't use menu!!
Pierre.
Hi Pierre
I had that problem for about 5 days and only reported it at the end of that period when I was relatively sure it was a real problem.
Naturally, after several reboots in the interim, AND testing with several large pngs this morning, I cannot reproduce it today. So sorry! I don't think it was a red herring though, because the images were corrupted. Luckily I had backups, only lost my editing sessions.
If I switch to another app while XNView is saving, then the XNView close control becomes active and clicking it gives the "not responding" alert. but I think this is normal behavior.
I've been trying to document weird XNView behavior I have encountered while XNView is open as a viewer AND TotalCommander/XNView thumbnail creation is in progress. It seems that XNView gets confused when it has been asked to create TC thumbnails and view/edit a file at the same time. Perhaps my PNG problem is related to that.
Nothing definitively reproducible for that problem, though. I'll post again when I do have something reproducible and will keep watching for the PNG behavior I reported.
Thanks.
I had that problem for about 5 days and only reported it at the end of that period when I was relatively sure it was a real problem.
Naturally, after several reboots in the interim, AND testing with several large pngs this morning, I cannot reproduce it today. So sorry! I don't think it was a red herring though, because the images were corrupted. Luckily I had backups, only lost my editing sessions.
If I switch to another app while XNView is saving, then the XNView close control becomes active and clicking it gives the "not responding" alert. but I think this is normal behavior.
I've been trying to document weird XNView behavior I have encountered while XNView is open as a viewer AND TotalCommander/XNView thumbnail creation is in progress. It seems that XNView gets confused when it has been asked to create TC thumbnails and view/edit a file at the same time. Perhaps my PNG problem is related to that.
Nothing definitively reproducible for that problem, though. I'll post again when I do have something reproducible and will keep watching for the PNG behavior I reported.
Thanks.
John
Sorry to have to bump this thread, but I had the large PNG corruption problem again yesterday.
Using Version 1.82.4.
XnView was in the middle of saving a large JPG as a PNG and I accidentally clicked the close control on XnView's window.
XnView closed immediately. It should have said "Wait a sec, I'm busy", instead.
The PNG was corrupted. Of course I lost all my changes to the JPG, too.
Using Version 1.82.4.
XnView was in the middle of saving a large JPG as a PNG and I accidentally clicked the close control on XnView's window.
XnView closed immediately. It should have said "Wait a sec, I'm busy", instead.
The PNG was corrupted. Of course I lost all my changes to the JPG, too.
John
You can close xnview window while you save png?JohnFredC wrote:Sorry to have to bump this thread, but I had the large PNG corruption problem again yesterday.
Using Version 1.82.4.
XnView was in the middle of saving a large JPG as a PNG and I accidentally clicked the close control on XnView's window.
XnView closed immediately. It should have said "Wait a sec, I'm busy", instead.
The PNG was corrupted. Of course I lost all my changes to the JPG, too.
Pierre.
Which size----
—> JohnFredC
Hello John!
• In your start-message, you said that the bug occurs for 100-MiB files.
- Indeed, such files are rather rare, and not easy to find on the Web !
- Naturally, I could try to build one "fancy" i.e. making a huge strip of images to test, but this shouln't be very realistic, and could take ages…
- Hence, please could you tell us wich minimal size is able to produce that bug ?
Maybe do you know how to get one file in that "minimal" size ?
- Thank you !
Kind regards,
Claude
Clo
Hello John!• In your start-message, you said that the bug occurs for 100-MiB files.
- Indeed, such files are rather rare, and not easy to find on the Web !
- Naturally, I could try to build one "fancy" i.e. making a huge strip of images to test, but this shouln't be very realistic, and could take ages…
- Hence, please could you tell us wich minimal size is able to produce that bug ?
Maybe do you know how to get one file in that "minimal" size ?
- Thank you !
Kind regards,Claude
Clo
Old user ON SELECTIVE STRIKE till further notice •
Hi Clo!
I cannot always reproduce the bug.
I make my big images by stitching many (20-50) 4-megapixel images into wall-sized panoramas. However, if you need big images, NASA gots lotsa BIG images. Beautiful ones too!
For instance...
Try this latest Mars image from the new Mars Reconnaisance Orbiter. WARNING! This is a 20Mb JPG, 20,050x9,500. Try saving it as a PNG from XnView and 2/3 of the way through the save close the main XnView window with the upper-right window control (the "X").
The parent page for this image is here:
http://www.nasa.gov/mission_pages/MRO/m ... 08014.html
The actual image can be got directly from here:
http://photojournal.jpl.nasa.gov/jpeg/PIA08014.jpg
There is a 190Mb TIFF of it available for download too!
Or try this page for a large wonderful view from the Hubble space telescope. "Large" means 59Mb JPG, 15,852 x 12,392. Scroll down for the link.
http://imgsrc.hubblesite.org/hu/db/2006 ... ll_jpg.jpg
Here's an even bigger image, 16,000 x 16,000! Smaller JPG file, though: "only" 24Mb. Scroll down for the link.
http://hubblesite.org/newscenter/newsde ... age/a+warn
XnView does a pretty decent job with these except for the saving issue I reported here. I do wish XnView supported that fly-over scrolling (click middle mouse button, then just move the mouse, like in Internet Explorer) that I requested in another thread. Keeping the mouse button down in order to "fly" around these images is a literal pain in the hand.
I cannot always reproduce the bug.
I make my big images by stitching many (20-50) 4-megapixel images into wall-sized panoramas. However, if you need big images, NASA gots lotsa BIG images. Beautiful ones too!
For instance...
Try this latest Mars image from the new Mars Reconnaisance Orbiter. WARNING! This is a 20Mb JPG, 20,050x9,500. Try saving it as a PNG from XnView and 2/3 of the way through the save close the main XnView window with the upper-right window control (the "X").
The parent page for this image is here:
http://www.nasa.gov/mission_pages/MRO/m ... 08014.html
The actual image can be got directly from here:
http://photojournal.jpl.nasa.gov/jpeg/PIA08014.jpg
There is a 190Mb TIFF of it available for download too!
Or try this page for a large wonderful view from the Hubble space telescope. "Large" means 59Mb JPG, 15,852 x 12,392. Scroll down for the link.
http://imgsrc.hubblesite.org/hu/db/2006 ... ll_jpg.jpg
Here's an even bigger image, 16,000 x 16,000! Smaller JPG file, though: "only" 24Mb. Scroll down for the link.
http://hubblesite.org/newscenter/newsde ... age/a+warn
XnView does a pretty decent job with these except for the saving issue I reported here. I do wish XnView supported that fly-over scrolling (click middle mouse button, then just move the mouse, like in Internet Explorer) that I requested in another thread. Keeping the mouse button down in order to "fly" around these images is a literal pain in the hand.
John
Snail…
—> JohnFredC
Hi John !
• Thank you very much for these sample-sources !
• I got the <PIA08014.jpg> and saved it as PNG. OMG ! The output size is 80.76 MiB !
You have time enough to prepare and drink several cups of coffee (with toasts !)
• All along this snail-ride, I attempted to close XnView, I began while I saw ~30% on the progress-bar.
- However, I got the error-sound always, and the same with the [x] button of the current window, error sound and no close.
- I tried too to minimize the window or the programme, nope ! Same error sound, and for that, I guess it's abnormal !
- Finally, the conversion has been successful, so I couln't get the bug this time…
- Aside, just some thoughts¦remarks :
• On one hand, the progress-bar is not very meaningful - especially as "dashed", because its control looks quite full while the conversion is not ended yet. I guess it's due to the dashed graphism (each item is not resized with regard to the whole size…) and a too narrow control for the bar.
- We miss the progress display in the status-bar as digital too, it should be very useful in such cases. Or else, use an old style solid full bar automatically as a workaround, let's say when the size of the processed picture is greater than nn… MiB.
• On the other hand, I think that such an operation could be performed in the background - in another thread - since currently the whole PC is frozen…
- Test under Win XP-Pro - SP1 - P4 @ 2.4 GHz - 512 MiB DD-RAM
- I'll test again when I'll have my 2-CPU machine available again with 1 GiB RAM… Just find the time to repair and reinstall it !
Kind regards,
Claude
Clo
Hi John !• Thank you very much for these sample-sources !
• I got the <PIA08014.jpg> and saved it as PNG. OMG ! The output size is 80.76 MiB !
You have time enough to prepare and drink several cups of coffee (with toasts !)
• All along this snail-ride, I attempted to close XnView, I began while I saw ~30% on the progress-bar.
- However, I got the error-sound always, and the same with the [x] button of the current window, error sound and no close.
- I tried too to minimize the window or the programme, nope ! Same error sound, and for that, I guess it's abnormal !
- Finally, the conversion has been successful, so I couln't get the bug this time…
- Aside, just some thoughts¦remarks :
• On one hand, the progress-bar is not very meaningful - especially as "dashed", because its control looks quite full while the conversion is not ended yet. I guess it's due to the dashed graphism (each item is not resized with regard to the whole size…) and a too narrow control for the bar.
- We miss the progress display in the status-bar as digital too, it should be very useful in such cases. Or else, use an old style solid full bar automatically as a workaround, let's say when the size of the processed picture is greater than nn… MiB.
• On the other hand, I think that such an operation could be performed in the background - in another thread - since currently the whole PC is frozen…
- Test under Win XP-Pro - SP1 - P4 @ 2.4 GHz - 512 MiB DD-RAM
- I'll test again when I'll have my 2-CPU machine available again with 1 GiB RAM… Just find the time to repair and reinstall it !
Kind regards,Claude
Clo
Old user ON SELECTIVE STRIKE till further notice •