[Bug 537898] New: cdrdao-1.2.2-310.12: memory leak
http://bugzilla.novell.com/show_bug.cgi?id=537898 Summary: cdrdao-1.2.2-310.12: memory leak Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dcb314@hotmail.com QAContact: qa@suse.de Found By: --- I just had a look at factory package cdrdao-1.2.2-310.12 For source code file cdrdao-1.2.2/xdao/TrackManager.cc around line 240, function TrackManager::update, is the following code ent = new Entry(t, trackNr, index, 0); but earlier is the code if (startLba < tstart.lba()) { // 'start' is in pre-gap of track ent = new Entry(t, trackNr, 0, 0); so there are two calls to new on ent, but no call to delete between them. This looks like a memory leak to me. Suggest rework code so that the two calls to new are avoided. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537898 Marcus Meissner <meissner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |nadvornik@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=537898 User rguenther@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=537898#c1 --- Comment #1 from Richard Guenther <rguenther@novell.com> 2009-10-17 08:55:29 MDT --- David, in case the issues are not introduced by a patch local to openSUSE please report the issues upstream. Packagers, please do not add openSUSE-local patches to fix this kind of errors but forward the bugs upstream and close the bugs as RESOLVED UPSTREAM. Note that it is perfectly fine to have "resource leaks" at the end of a program as the kernel will clean up for you. Manually freeing them only increases binary size and runtime. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com