On Mar 25, 2006, at 3:42 , Chris Little wrote:

on 3/25/06 8:05 AM, Sven E Olsson at [EMAIL PROTECTED] wrote:

EditField Memory Leak RB2006r1 OS X 10.4.5 ??


I have build an small test app with an EditField. (About 9MB used
Memory when I opened the app)

1 - I Open an 1.8 MB Text File and the memory used is 115.36MB!
2 - I close the Window and now the used memory is 113.14MB!
3 - When the 1.8MB File is loaded the CPU usage is about 50 - 60%
(The EditField is only active)

4 - I have done this test about 10 - 20 times, and the lowest memory
usage after closing the window
was 102MB.



Note: This is NOT an 'Complain', it is some facts that i have to try
fix in one or another way!

My test app is available: http://www.okraft.nu/seedit/tmp/
EditFieldTest-2.zip

Any Ideas how to fix this problems are welcome!

How are you measuring the memory usage? Does the memory usage grow if you
open, close, open, close, ...?

I use the Activity Monitor...

Nope, It looks like you said, it is allocated the first time, and only grows an MB when I opened the file
and then when i close i get an MB less. But still over 100MB alloctaed


If it doesn't then what you're seeing isn't leak but how RB does memory allocation. I believe that RB asks the OS for a block of memory and then
sub-allocates from that.


An EditField isn't always the best tool for the job. I'm guessing that it
has a fair overhead per paragraph and that's what you're seeing.


I understand that for some years, ago, but then i should test the latest version and found this,. The EditField is still not useful to load bigger files. (what is an big file today?)

Thanks for you response, and I think there is a lot of users, that now would
check it up before they use it in the same way.

I have an 'Fix' for this problem, so 'it works for me'  ...


Sven E Olsson


_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to