Your message dated Sat, 26 Aug 2006 17:41:41 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bugs #383030 & #383402 fixed in most recent upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libmusicbrainz4-dev
Version: 2.1.2
When doing normal query operations with the musicbrainz C interface, it
leaks memory like a sieve because mb_Delete() doesn't actually free
the RDF parser object. Patch is attached.
--
Ian Gulliver
Penguin Hosting
"Failure is not an option; it comes bundled with your Microsoft products."
diff -Naur libmusicbrainz-2.1.2/lib/rdfextract.cpp
libmusicbrainz-2.1.2.mod/lib/rdfextract.cpp
--- libmusicbrainz-2.1.2/lib/rdfextract.cpp 2004-10-12 10:10:46.000000000
+0200
+++ libmusicbrainz-2.1.2.mod/lib/rdfextract.cpp 2006-08-16 03:59:15.000000000
+0200
@@ -52,8 +52,6 @@
RDFExtract::RDFExtract(const string &rdfDocument, bool useUTF8)
{
- RDF_Parser parser;
-
hasError = false;
this->useUTF8 = useUTF8;
@@ -77,7 +75,7 @@
RDFExtract::~RDFExtract(void)
{
-
+ RDF_ParserFree (parser);
}
void RDFExtract::StatementHandler(RDF_SubjectType subject_type,
diff -Naur libmusicbrainz-2.1.2/lib/rdfextract.h
libmusicbrainz-2.1.2.mod/lib/rdfextract.h
--- libmusicbrainz-2.1.2/lib/rdfextract.h 2004-10-12 09:28:44.000000000
+0200
+++ libmusicbrainz-2.1.2.mod/lib/rdfextract.h 2006-08-16 03:59:04.000000000
+0200
@@ -70,6 +70,7 @@
private:
+ RDF_Parser parser;
vector<RDFStatement> triples;
string error, empty, retValue, count;
bool useUTF8, hasError;
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Bugs #383030 & #383402 fixed in most recent upload.
--
Jens Peter Secher
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
--- End Message ---
