/usr/bin/gs:11:gs_heap_resize_object:gdev_prn_allocate:gdev_prn_reallocate_memory:gdev_prn_maybe_realloc_memory:gdev_prn_put_params

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding ghostscript. This problem was most recently seen with version 9.15+dfsg-0ubuntu2.1, the problem page at https://errors.ubuntu.com/problem/6dd9900ffacad91c9d351ad2b5bdfceaaff5389f contains more details.

[Till Kamppeter (till-kamppeter)]

Problem seems to be solved from Ghostscript 9.16 on as it only happened with 9.15. 9.16 is used in Wily (15.10), so an upgrade to this Ubuntu version will most probabvly fix it.

The problem happens only with the "cups" output device of Ghostscript. Assuming the bug being there, we could look at the changes of the "cups" output device from 9.15 to 9.16. There is only one and this one is even a crasher fix:

http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=7d97b54d767627d1d88ea026c3d3accd11cb670f

One could think this has solved it, but it does not really fit to the backtrace in the error tracker. So one would even need a reproducer for this bug so that one can try with and without the mentioned fix or one needs contact to the contributors of the error reports (there is no Launchpad bug report about this problem) to let the contributors doing tests.

I will not do an SRU as I am not sure whether the mentioned fix helps and I also do not have a reproducer and/or someone to test and verify the SRU. Closing ...

[Brian Murray (brian-murray)]

One way to verify the SRU is by confirming that the new package version does not appear in the list of affected packages in the Error Tracker's bucket.

[Till Kamppeter (till-kamppeter)]

If I would apply this patch and upload the resulting package, no one would download and test it. How should this SRU get verified?