summaryrefslogtreecommitdiff
path: root/source/fitz/memory.c
diff options
context:
space:
mode:
authorRobin Watts <robin@peeves.(none)>2013-11-27 03:24:43 -0800
committerRobin Watts <robin.watts@artifex.com>2013-11-27 11:28:38 +0000
commita290828ad27a30b894e7bc11f77b612e8cec83a8 (patch)
treea1b28a508a237c910c518cc8c15e210bc5a1b790 /source/fitz/memory.c
parentb1ed116091b790223a976eca2381da2875341e10 (diff)
downloadmupdf-a290828ad27a30b894e7bc11f77b612e8cec83a8.tar.xz
Bug 694116: Solve valgrind issues in draw device.
The actual issue here is that a pixmap is dropped more times than it should be due to an error in the rendering pipeline. The problem arises because we fail to push a clip image mask, but still pop the mask off the stack later. This puts us off by 1 in the stack handling. The simplest solution to this (that will be safe no matter what mistakes are made by the caller too) is to add some simple tests in the draw device to ensure we do not free too early.
Diffstat (limited to 'source/fitz/memory.c')
0 files changed, 0 insertions, 0 deletions