On Mon, 2005-05-23 at 09:56 +0200, Gour wrote:
Duncan Coutts (duncan.coutts@worc.ox.ac.uk) wrote:
Yes I think that's right. I did quite a bit of profiling work last year and I didn't notice anything that looked to me like a space leak.
Huh...I'm a little bit puzzled now 'cause on dev list the discussion was going on about 'space leaks'.
Well it wasn't me :-). The typical cause of vast memory consumption is a space leak, so it's often something people mention.
Anyway, the facts remains the same for the end user: it's not possible to build gtk2hs without having enormous amount of RAM.
Both reasonable. We'll keep that in mind if we try for a heap reduction patch.
Am I right assuming that this could be even more difficult than fixing (non-existant) space leak?
Hard to say. :-) It means changing algorithms and/or data structures rather than trying to indentify and understand space leaks.
I think if I were to try this again, I'd try and make the name analysis phase into an external algorithm, keeping as much of the various finite maps in external files for most of the time.
Let me know if I can help with some sort of testing.
Ok. Duncan