Project

General

Profile

Bug #780

Memory leak

Added by Thomas Capricelli about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Category:
General
Target version:
Start date:
12/11/2011
Due date:
% Done:

100%

Estimated time:

Description

As seen using tools such as valgrind, there's indeed actually several memory leaks. There are at least
  • one dealing with the parser (parseFromString(), based on flex/bison)
  • one dealing with allocation/freeing of "BaseElement"
  • maybe others.

Related issues

Related to Symia - Bug #774: Memory bugClosed10/27/2011

Actions
Related to Symia - Bug #775: Response 774 bugRejected10/29/2011

Actions

Associated revisions

Revision 107:db609745c24b (diff)
Added by Thomas Capricelli about 9 years ago

fix ugly and obvious bug due to quick&dirty&untested copy/paste. Fix a big
memory leak.
refs #780

Revision 110:4f1a2de5911e (diff)
Added by Thomas Capricelli about 9 years ago

fix another memory leak by explicitely defining some constructors. It seems
the default behaviour is not the obvious expected one. With this patch,
valgrind now reports "All heap blocks were freed -- no leaks are possible"
on some test examples I'm using, which were previously all wrong.
There's still a small leak (~300 bytes) on our own 'test' binary, but it
seems related to Qt tests rather than the symia code.
Definitely fixes #780

History

#1

Updated by Thomas Capricelli about 9 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Applied in changeset 4f1a2de5911e.

Also available in: Atom PDF