Bug 50892 - Memory leak / Invalid PageViewports stored in IDTracker
Summary: Memory leak / Invalid PageViewports stored in IDTracker
Status: NEEDINFO
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: general (show other bugs)
Version: all
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-08 09:34 UTC by Martin K
Modified: 2012-04-24 05:34 UTC (History)
1 user (show)


Attachments
Workaround: Replace old references in IDTracker (5.24 KB, patch)
2011-03-08 09:35 UTC, Martin K 		Details | Diff
View All 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 Martin K 2011-03-08 09:34:34 UTC 
PageViewports are added to the IDTracker, while content is put into them.
The PageProvider discards PageViewports under some conditions (discardCacheStartingWith) - the result is, that the ID Tracker has references to the old PageViewport while the new PageViewport is used for rendering. 

There is a memory leak, as some content is put on the old PageViewport first, before generating the new PageViewport. The content of the new PageViewport is freed during rendering - the content of the old PageViewport is not freed.
Comment 1 Martin K 2011-03-08 09:35:27 UTC 
Created attachment 26744 [details]
Workaround: Replace old references in IDTracker
Comment 2 Glenn Adams 2012-04-07 01:44:18 UTC 
resetting P2 open bugs to P3 pending further review
Comment 3 Glenn Adams 2012-04-08 05:06:45 UTC 
please provide minimal input FO file, output PDF file(s), and all console output demonstrating problem
Comment 4 Glenn Adams 2012-04-24 05:34:49 UTC 
(In reply to comment #3)
> please provide minimal input FO file, output PDF file(s), and all console
> output demonstrating problem

Martin, I am still awaiting your input as requested above. if I see no further input by April 30, I will close this bug due to lack of requested information. Regards, Glenn