This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 217516 - Memory leak in spellchecker
Summary: Memory leak in spellchecker
Status: RESOLVED DUPLICATE of bug 207412
Alias: None
Product: editor
Classification: Unclassified
Component: Spellchecker (show other bugs)
Version: 7.2
Hardware: PC Linux
: P2 normal (vote)
Assignee: Jan Lahoda
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2012-08-28 11:22 UTC by Petr Cyhelsky
Modified: 2012-10-19 05:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

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 Petr Cyhelsky 2012-08-28 11:22:33 UTC 
The heap dump is at: http://netbeans.org/projects/profiler/downloads/download/Heapdumps/Heapdump1345649979357.hprof.gz

It seems spellchecker is preventing editor document from being garbage collected - see NbEditorDocument #2 in the heapdump.
Comment 1 David Strupl 2012-09-12 10:57:57 UTC 
I will have a look.
Comment 2 Jan Lahoda 2012-09-12 11:36:29 UTC 
IIRC, Petr should evaluate the effect of fix for bug #207412:
http://hg.netbeans.org/main-golden/rev/bd468fbf57b4
possibly with some adjustments to the test, and let us know whether that patch is sufficient or not.
Comment 3 David Strupl 2012-09-12 12:47:30 UTC 
Returning to Lahvac. From the thread dump it seems that the spellchecker's updateVisibleSpans worker was still running when the test was taking the thread dump. I don't know whether it means that the spellchecker did not finish or whether it would be enough if the test waited a little longer before taking the snaphost.
Comment 4 Petr Cyhelsky 2012-10-05 11:03:31 UTC 
The leak is no longer present in memory tests, so from my point of view, it is fixed and you can close the issue.
Comment 5 Jan Lahoda 2012-10-19 05:45:54 UTC 
Ok, thanks.

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