Customer reports files do not display at 72 dpi or at 20 dpi (but does work at 1bpp and 20 dpi). I have confirmed with HEAD. Parsing an image in the file results in two calls to gs_heap_alloc_bytes() requesting 2GB. This fails and is reported as: **** Warning: File encountered 'VMerror' error while processing an image. Several objects later, gs segfaults in gstate_free_contents(). So there may be two bugs here: whatever's generating the spurious allocation request, and not handling its failure cleanly.
Created attachment 2180 [details] sl08jan2006in023.pdf first problem example
Created attachment 2181 [details] stl12dec2005re002.pdf second example file
We believe this is another example of the pattern accumulator issue. q.v. Bug #688396. The resolution is to avoid using the accumulator when the pattern is larger than a certain size. Embedding patterns as high level objects in the clist will help when using the clist, but the accumulator change is still necessary for display devices, etc. See details attached to 396. *** This bug has been marked as a duplicate of 688396 ***
Changing customer bugs that have been resolved more than a year ago to closed.