Filip Konvička wrote:
what is the exact meaning of {Property.get 'gc'}.size ?
The documentation says: "Current heap size in bytes". This is not the
current *maximum* heap size, but what is currently in use.
> I have a large
problem that consumes quite a lot of memory. When I look into the Task
Manager, I can see that the emulator consumes say 100MB of memory, but
at the same time, {Property.get 'gc'}.size tells me that the heap size
is just about 10 MB.
Possibly your program creates a large amount of temporary data.
I ask because my program ends up at about 1 GB :-) Because the solver
runs in a loop, I tried to make sure that the loops do not leave
temporary data behind. However, I still think that each loop leaves some
footprint, so I'm trying to identify the culprit... are there some known
memory leaks in the emulator? It seems that the data and heap size grow
quite reasonably, but the real memory consumption of the emulator
process is suspicious...
IIRC there is no known memory leak in the last release. Anyway if you
find one, please send a bug report with a small program the reproduces
the bug.
I suggest to check your program first. Are you building very huge data
structures that you keep in a global variable? Are you using a port
whose stream is kept in a global variable (pretty common mistake)? Or
an infinite amount of threads waiting on each other?
Cheers,
raph
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
