Hi Eliot, The images are loaded into memory only when they need to be presented in the visible part of the screen. Unfortunately in memory the images are not archived anymore as JPEG's so a JPEG could have a much larger memory footprint (probably equivalent to a BMP representation of it on disk). What we fixed is that if the image fails to be loaded in the memory the dialog does no longer pop-up and instead of the image an error message is seen in the Author view (just like when you have an invalid path to the image and it cannot be found). The errors loop occurs now because the error dialog gets presented and when you cancel it the image is again in the visible part of the screen and another image reload is performed which fails in the same manner. That's why after you open a new editor by Drag and Drop the image is not in the visible part of the screen anymore so it will not be loaded anymore. Can you tell us the resolution of the JPEG image and the color depth? We'll try to approximate the footprint it may have in memory. As a workaround you can increase the memory amount given to Oxygen from the link I posted in the previous mail: http://www.oxygenxml.com/doc/ug-standalone/installation-instructions.html#se... Regards, Radu -- Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Eliot Kimber wrote:
I noticed that if I open new file with Oxygen from outside Oxygen (e.g., drop file onto Oxygen icon in the Dock) that that file opens fine and I can quit the currently-open message box and then quit Oxygen. However, if I switch back to the original doc, I'm back in the message loop.
Cheers,
E.