To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=100905


User af changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |FIXED
--------------------------------------------------------------------------------




------- Additional comments from [email protected] Thu Apr 16 15:41:42 +0000 
2009 -------
Ah, Linux to the rescue.  Tried to reproduce the crash on Linux to find the
memory leak and found something different.  It is not a memory leak at all but a
simple, old-fashioned NULL pointer access.  Not sure why the Windows stack
traces looked so different.

Again the conversion of polygon to region is the cause.  (One of my recent
enhancements, should have tested this better.)  A polygon is split into
rectangles that are stored in horizontal bands (all rectangles in one band have
the same height and do not overlap).  In the case that the bottom most band
should have a height of one pixel this band was never created.  The resulting
NULL pointer was not checked and caused the crash.

Fixed by a) creating the one pixel high band and b) by handling NULL pointers
gracefully.

SVN revision of the fix in vcl/source/gdi/region.cxx and regband.cxx is 270896.


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to