From: SourceForge.net <no...@so...> - 2006-06-19 13:09:24
|
Bugs item #1508457, was opened at 2006-06-19 08:06 Message generated for change (Comment added) made by dwarren You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101176&aid=1508457&group_id=1176 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: C interface Group: Other Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Memory leak? Initial Comment: I have a problem using xsb_query and xsb_query_string. after few query, memory used by program gorw up 300 Mb... Is it a memory leak problem? I attached a file with the method's source code that use c interface. In this file I use xsb_query, but I have the same problem using xsb_query_string. ale...@ti... ---------------------------------------------------------------------- >Comment By: David S. Warren (dwarren) Date: 2006-06-19 13:09 Message: Logged In: YES user_id=13069 Some small(?) memory leaks in the C-interface were fixed about 7 months ago, so they are not in the current release. Are you using the release or a more recent check-out from cvs? If the release, then it may be fixed. On the other hand 300MB is a lot of leak for this (I avoided keeping the strings that were the queries around in atom space.) Also, you should run "statistics" when you have the 300MB allocated, and see where the memory is being used. (Another recent change makes statistics give more information about how memory is being used.) -David ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101176&aid=1508457&group_id=1176 |