PATCH: memory leak in VanDale.py parser

Bug #194779 reported by Wesley Stessens
2
Affects Status Importance Assigned to Milestone
GtkVD
Fix Released
Medium
Roel Huybrechts

Bug Description

There is a memory leak in the VanDale.py parser.
When a VanDale-parser instance is created, it never gets destructed.
This will steadily increase memory usage when more searches are being done.
Attached patch against rev 103 will fix the problem.

Revision history for this message
Wesley Stessens (wesley) wrote :

Okay. This doesn't actually fix the bug, it just makes the bug less severe.
The VanDale instance gets destructed, but the Parser class still doesn't..
This is actually not a good patch. I will try to find the problem in the Parser itself..

Revision history for this message
Wesley Stessens (wesley) wrote :

This updated patch against rev 103 will completely fix the memory leak.
The parser is not subclassed from BeautifulSoup anywhere. This was giving problems?
All destructors are now called like they should. Memory usage is stable.

Revision history for this message
Roel Huybrechts (rulus) wrote :

Thanks a lot for looking into this and for the patch. It's now commited in the trunk branch and will be in the next version.

Changed in gtkvd:
assignee: nobody → rulus
importance: Undecided → Medium
milestone: none → 0.4.4
status: New → Fix Committed
Revision history for this message
Roel Huybrechts (rulus) wrote :

The patch is included in the recently released version 0.4.4. Thanks again!

Changed in gtkvd:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.