Bug 693927 - Regression: /VMerror starting with 5403b7384b203c6b462f8ed3190b7962c929769c
Summary: Regression: /VMerror starting with 5403b7384b203c6b462f8ed3190b7962c929769c
Status: RESOLVED DUPLICATE of bug 689805
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Images (show other bugs)
Version: master
Hardware: PC All
: P2 normal
Assignee: Michael Vrhel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-20 20:57 UTC by Marcos H. Woehrmann
Modified: 2013-07-23 09:22 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marcos H. Woehrmann 2013-04-20 20:57:41 UTC 
Starting with 5403b7384b203c6b462f8ed3190b7962c929769c a couple of the nightly regression tests fail with a /VMerror.  Here is an example command line:

  bin/gs -o test.pxl -sDEVICE=pxlcolor -r300 ./Bug692688.pdf

The other file that shows the same error is Bug692933.pdf
Comment 1 Chris Liddell (chrisl) 2013-04-22 12:18:58 UTC 
Both of those give me VMerrors with commit prior to the one mentioned - as a result of trying to allocate more than 2Gb in the transparency code.

Assigning back to Marcos for further information.......
Comment 2 Marcos H. Woehrmann 2013-06-03 04:07:11 UTC 
I've double checked and there is definitely a /Vmerror in 5403b7384b203c6b462f8ed3190b7962c929769c and not in 693c516ad22bb79d7c8c85329ff6a53dc82505fc, however I agree that allocating 2 gigs of memory is not reasonable so presumably the change just exposed the problem.

Assigning to Michael since he is the transparency go to person.
Comment 3 Ray Johnston 2013-06-03 16:00:45 UTC 
This should be resolved by my pending change to use a clist when the
pdf14 device would consume too much memory. I suggest that this be made
a duplicate of bug 689805.

If you agree, Marcos or Michael, please go ahead and resolve this as a
duplicate.
Comment 4 Marcos H. Woehrmann 2013-07-23 09:22:20 UTC 

*** This bug has been marked as a duplicate of bug 689805 ***