problem with importing JPEG-images

dackel · Newbie Joined: 20 Mar 2004 Posts: 2

Hello

When importing and then saving images into office writer, an error occurs: not enough virtuell memory.
Instead of an image appears a red lined window saying: reading error. Although I put the cache memory to maximum as well as the number of imported images and their size, it doesn't work.
The size of one image is 3-4 MB. Theoretically about 25 images should be imported, in real 6 images always got lost.

My PC has 512 MB cache memory, actually it should have worked.
Can you help me??
Sabine

dfrench · Posted: Sat Mar 20, 2004 12:34 pm Post subject:

Operating system?
How much virtual memory have you available? using at time of failure? is it a fixed allocation or is windows automatically extending it for you? is there disk space to extend virtual memory to?
How much physical memory have you?
What is the memory allocation of soffice when only this document is open?
Are you recording changes to the document?
If you explore the .sxw as a zip archive (with winzip or similar) you will see the sizes of the various components of the document. Each graphic is an individual file (as JPEGs they will not be further compressed in the zip archive). Are you seeing what you expect?

dackel · Newbie Joined: 20 Mar 2004 Posts: 2

Operating system is Win2kSP4. Physical memory is 512 MB. Virtual memory is a fixed allocation of 2.5 x physical memory (=1280 MB). There is enough disk space to extend virtual memory. The total size of the document is 18.3 MB. There were 28 pictures imported into the document, with each picture of about 2-3 MB. When I explore the .sxw file with winzip, it shows me only 7 pictures, each with the correct size.
Any ideas? Thank you.

dfrench · Posted: Sat Mar 20, 2004 9:13 pm Post subject:

The message "not enough virtual memory" is a win2k thing. To point the finger successfully at OOo you need to show that doing a particular insert is requesting a massive amount of (virtual) memory. Perfmon.exe is a good tool for capturing information about resource utilisation. If you set it to record the increasing committed memory as your jpeg files are added you may see the event which is causing the problem and have some diagnostic info to add to a bug report.