On Mittwoch, 14. Januar 2009, zehet...@molgen.mpg.de wrote:
> I think it's objects creating new objects whose memory is than never
> released even if the first object is unset.(most likely the php problem as
> described in the link you sent me in your original reply). I tried to keep
> track where
I think it's objects creating new objects whose memory is than never released
even if the first object is unset.(most likely the php problem as described in
the link you sent me in your original reply). I tried to keep track where which
objects are created but I became quickly rather confused. I co
Ok, thanks for this first analysis. The built-in MW profiling actually reports
memory usage as well. This might further increase our understanding of the
issue. But ultimately, some detailed report on memory usage for allocated data
structures in PHP would be most valuable to find out what reall
Thanks for the info.
Actually the MySQL version I mistyped it is 5.0.45 not 6.0.45
I'll see if I can update PHP sometime.
Cheers,
Gu
btw I solved my specific original problem by avoiding any objects and therefore
memory leaks altogether.
Quoting CNIT :
>
> > Hi,
> >
> > I wonder if anyone c
> Hi,
>
> I wonder if anyone can tell me if the functions used when I call
> SMWQueryProcessor::getResultFromQueryString should release all the memory
> after
> they finished?
>
> I thought I could avoid a memory problem by calling getResultFromQueryString
> with different 'offset' values to retr
Hi,
I added some memory_get_usage() calls to the code
'before' is the return value before the call to
SMWQueryProcessor::getResultFromQueryString (with different offset values)
'#1' value in getInstanceQueryResult() after
$result = new SMWQueryResult()
'#2' value in getInstanceQueryResult()
Hi,
I am not aware of a good way of debugging memory issues in PHP yet. Can anyone
recommend a free profiler or the like? As for your problem, there is a general
tendency of PHP to hoard memory during (very) long runs. This is a known bug
that apparently can only be avoided by re-engineering th
Hi,
I wonder if anyone can tell me if the functions used when I call
SMWQueryProcessor::getResultFromQueryString should release all the memory after
they finished?
I thought I could avoid a memory problem by calling getResultFromQueryString
with different 'offset' values to retrieve smaller chunk
