On 07/02/2014 10:29 PM, Fabián Mandelbaum wrote:
Just one more technical detail regarding our experience with this issue:
Increasing memory (-Xmx) did not help us that much. I cannot remember if
we went up to 2048m, but I'm 100% sure we've tried with 1024m with same
results.
The only workaround for this issue we were experiencing was to remove
duplicated IDs, thus minimizing validation errors.
Thank you for this information. However, in our experience, the case of
an XXE user working on a huge XML document containing loads of images is
more common than having to cope with an XML document having 30,000
cross-reference errors.
When our XXE user attempts to open his DocBook document which is 2,000
pages when printed, over 700 XML ``xincluded'' files, just over 1100
<imagedata> elements, facing out of memory errors is not surprising at
all, and can indeed be fixed by increasing the amount of memory allowed
for Java.
Some hard facts:
In Java, on screen, 1 image pixel = 4 bytes (RGBA).
Let's suppose the document contains screenshots which have the average
size of 500x500 pixels.
1100*500*500*4 = 1,100,000,000 bytes = 1,049 Mb = 1.02 Gb
By default, XXE instructs Java to use up to 512Mb (which is already
enormous). This means, that for use cases such as the above one, out of
memory errors are guaranteed to happen.
--
XMLmind XML Editor Support List
[email protected]
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
