Not enough memory bug
Moderators: XnTriq, helmut, xnview
-
- Posts: 79
- Joined: Thu Dec 15, 2005 10:59 am
- Location: Germany
- Contact:
Not enough memory bug
Hello,
I want to open an .tiff file via XNView file browser and when clicking on it in the list, it says "Not enough memory". If I open the picture before it in the list and then switch to the tiff file it is opened, as expected.
Happens in 1.92, too.
(Not that really annoying bug, because normally I have much memory free, but now an full virus scan 8antivir free) runs, which eats full 2GB...
XNView is great! I really won't miss it anymore!
Update: XNView seems to eat memory when opening .tiff files. It needs 530000KB for an 64MB tiff file. The internal viewser of Win XP needs only 290000KB
regards,
Stefan
I want to open an .tiff file via XNView file browser and when clicking on it in the list, it says "Not enough memory". If I open the picture before it in the list and then switch to the tiff file it is opened, as expected.
Happens in 1.92, too.
(Not that really annoying bug, because normally I have much memory free, but now an full virus scan 8antivir free) runs, which eats full 2GB...
XNView is great! I really won't miss it anymore!
Update: XNView seems to eat memory when opening .tiff files. It needs 530000KB for an 64MB tiff file. The internal viewser of Win XP needs only 290000KB
regards,
Stefan
Hm, I thought this bug was fixed in v1.92.1
XnTriq ([url=http://newsgroup.xnview.com/viewtopic.php?p=57412#57412]1.91.6 : Halt upon exiting[/url]) wrote:Yes, a (write-protected) TIF image is the culprit.xnview wrote:Really, do you reproduce it?XnTriq wrote: I had the same problem today in browser mode (XnView v1.92 on Windows 2000 SP4).
MARCANNE [url=http://newsgroup.xnview.com/viewtopic.php?p=58246#58246]Mémoire insuffisante[/url] wrote:Je possède un PC avec 4 Mo de RAM, et avec XnView je souhaite ouvrir des photos en TIF de 1,5 Go chacune. Impossible de les lire, le logiciel indiquant "MEMOIRE INSUFFISANTE"
Quelqu'un a-t-il une idée ?
Re: B2: Not enough memory bug
Is it a B&W picture? How many pixels?surfacecleanerz wrote: Update: XNView seems to eat memory when opening .tiff files. It needs 530000KB for an 64MB tiff file. The internal viewser of Win XP needs only 290000KB
Pierre.
-
- Posts: 79
- Joined: Thu Dec 15, 2005 10:59 am
- Location: Germany
- Contact:
Hmmm... XnView has always had problems opening reasonably large images. See my old post here!
What kind of memory is that? RAM? Swap file? Video card?
I don't think XnView uses all available memory for displaying large files. I have a 4Gb swap file + ~450Mb of free RAM and the largest file that XnView will usually load is about 90Mb (it varies). With 4.5 Gb available, I would expect that (using the "times 10" formula) XnView should be able to open a 400Mb image without problem (though slowly, of course)...
But it won't!
Are you implying that is a general rule of thumb? Perhaps: Multiply the image file size by 10 to get the memory XnView needs to display it?xnview wrote:So you need 464Mb to load it
What kind of memory is that? RAM? Swap file? Video card?
I don't think XnView uses all available memory for displaying large files. I have a 4Gb swap file + ~450Mb of free RAM and the largest file that XnView will usually load is about 90Mb (it varies). With 4.5 Gb available, I would expect that (using the "times 10" formula) XnView should be able to open a 400Mb image without problem (though slowly, of course)...
But it won't!
John
Sorry but i don't understand. For a 15584x7792x32 picture, i need 15584x7792x4 bytesJohnFredC wrote:Hmmm... XnView has always had problems opening reasonably large images. See my old post here!
Are you implying that is a general rule of thumb? Perhaps: Multiply the image file size by 10 to get the memory XnView needs to display it?xnview wrote:So you need 464Mb to load it
What kind of memory is that? RAM? Swap file? Video card?
Pierre.
-
- Posts: 79
- Joined: Thu Dec 15, 2005 10:59 am
- Location: Germany
- Contact:
Hello,JohnFredC wrote:Hi Pierre
You responded (above)... where "it" was the 47.6Mb image posted by surfacecleanerz .So you need 464Mb to load it
That's approximately 10x the image filesize.
It's normal:
The 47.6Mbytes image is "compressed", but you need to open it (RAM memory and/or hdd swap) : 15584x7792x32bits picture = (15584x7792x4bytes)/(1024*1024)Mbytes = 463.23 Mb, then at lest 464Mb of memory.
The same file in B&W = 15584x7792x1bit = 14.47Mb
Oops, too late ! LOL
My image is LZW compressed, which should have a great affect, because 5ß% are transparent areas (because of a bug in the Panorama software...).
XnViewMP Linux X64 - Debian - X64
-
- Posts: 79
- Joined: Thu Dec 15, 2005 10:59 am
- Location: Germany
- Contact:
Re:
almost offtopic
* Some people need a transparent image to edit it instead of completition with a single colour or Smart Automatic Color Completition (kind of zoom from inside to outside, completing missing pixels (yours are transparent) with nearest color used in image)
* Try to align (rotate) panorama before render to minimise output file size
* Crop image removing small parts of it like white sky from left
No bug here! you have 1 transparent layer.surfacecleanerz wrote:My image is LZW compressed, which should have a great affect, because 5ß% are transparent areas (because of a bug in the Panorama software...).
* Some people need a transparent image to edit it instead of completition with a single colour or Smart Automatic Color Completition (kind of zoom from inside to outside, completing missing pixels (yours are transparent) with nearest color used in image)
* Try to align (rotate) panorama before render to minimise output file size
* Crop image removing small parts of it like white sky from left
Imi este indiferent ce cred ceilalti despre mine, caci oricum fiecare crede ce-i convine lui si nu ceea ce e real, doar ca mi-ar fi placut sa ma vada asa cum sint de fapt, nu asa cum poate le-ar placea lor sa creada. Ei au ales deja...