1. upper() problem now.....
- Posted by useless Sep 11, 2010
- 1056 views
Given the following code:
include std/text.e object temp, junk junk = "" for buildloop = 1 to 2000 do junk &= "a" end for for testloop = 1 to 1000000 do temp = upper(junk) end for
why is memory use steadily, and quickly, climbing until winxp says it's used too much and is terminated? It's not doing anything but calling upper() over and over, right?
No, not idle test code, i have an application crashing. Using v40b3, eui.
Hmm, ok, v4b4 isn't crashing. Upgrade to v4b4, people.
Wait, it is crashing, different problem tho. Must spec defaults in split().
useless
2. Re: upper() problem now.....
- Posted by mattlewis (admin) Sep 11, 2010
- 1049 views
why is memory use steadily, and quickly, climbing until winxp says it's used too much and is terminated? It's not doing anything but calling upper() over and over, right?
No, not idle test code, i have an application crashing. Using v40b3, eui.
Hmm, ok, v4b4 isn't crashing. Upgrade to v4b4, people.
Wait, it is crashing, different problem tho. Must spec defaults in split().
There was a memory leak in eu4b3 that was fixed. IIRC, it was related to a machine func or c_func call that was inlined. The temp wasn't being dereffed, I think.
Matt