[redland-dev] [Redland librdf RDF API 0000587]: memory leak in evaluation of results of SPARQL query with graph

Mantis Bug Tracker mantis-bug-sender at librdf.org
Sun Nov 9 13:49:38 EST 2014


The following issue has been SUBMITTED. 
====================================================================== 
http://bugs.librdf.org/mantis/view.php?id=587 
====================================================================== 
Reported By:                vandenoever
Assigned To:                
====================================================================== 
Project:                    Redland librdf RDF API
Issue ID:                   587
Category:                   api
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2014-11-09 10:49
Last Modified:              2014-11-09 10:49
====================================================================== 
Summary:                    memory leak in evaluation of results of SPARQL query
with graph
Description: 
There's memory leak in rdfproc when querying with GRAPH. This is also present in
custom c code.



Steps to Reproduce: 
echo "<http://example.com> <http://example.com> <http://example.com> ." >
triples.nt
rdfproc -c -s hashes test parse-stream triples.nt ntriples http://example.com
http://example.com
valgrind --leak-check=full --num-callers=20 rdfproc --contexts -s hashes test
query sparql11-query - "SELECT * WHERE { GRAPH ?g { ?s ?p ?o }}"
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2014-11-09 10:49 vandenoever    New Issue                                    
2014-11-09 10:49 vandenoever    File Added: valgrind.log                     
======================================================================



More information about the redland-dev mailing list