Re: memory leaks and colors
- Posted by useless_ Feb 09, 2013
- 1654 views
mattlewis said...
useless_ said...
Still awaiting a heads up for the version of Eu that has the leaks patched and the debugger colors fixed.
I'm not aware of any leaks in the current tips of either the 4.0 or 4.1 code (likewise, I've been told, though haven't personally verified that the debugger colors have been fixed). You've mentioned that you're still seeing some, but I have no idea where they're coming from. Do you have anything fairly minimal that reproduces it? If not, even the full thing would be helpful.
Matt
.. 3 am Friday 2/1/2013 .. [03:02] <useless2> other run-away memory leak happening [03:04] <useless2> i am heavily using match(), match_from(), match_all() [03:04] <useless2> memory use is bouncing from 80kb to 1.5Gb [03:05] <useless2> it's pushed pf use up to 4.5Gbytes [03:06] <useless2> just crashed : couldn't alloc 482156 bytes<snip>
.. 1 pm Friday 2/1/2013 .. [13:36] <useless2> using Euphoria-4.0.5-Jan30-2013 [13:36] <useless2> couldn't alloc 55200 bytes [13:36] <useless2> Your program has run out of memory. [13:36] <useless2> One moment please... .. 2 pm Friday 2/1/2013 .. [14:40] <useless2> ...We discussed it on irc 8 days ago:
.. 3 pm Friday 2/1/2013 .. [15:04] <mattlewis> hmm...that one should have the replace() memory leak fixed [15:05] <useless2> i agree [15:06] <mattlewis> I presume that your program releases the data? ...and this looks like another leak [15:06] <useless2> yeas, here's very few vars in use, each iteration assigns a new value (rather than appending)
Since it has been a week since i first asked about it, and you saying it should have been fixed, and now saying it is fixed, i didn't skinny the code down because it's plain you aren't interested in working with me on the problem.
If all leaks ARE fixed in the current release, what windows release is that? And is the color-fixed debug-trace included?
useless
