![]() The total memory allocated from OS never drops. , all disk and memory caches set to 'false'. Upon closing all the tabs and leaving one blank tab: I guess, the observed VM growth has nothing to do with any 'true' leaks, it rather concerns a behaviour of the glibc memory allocator.ģ. (default of both option is "-1", determined by memory size) _total_viewers=0(disabled) or N(enabled) (2) Check both 2 cases, bfcache=disabled case and bfcache=enabled case. (1) Set memory cache size manually, and keep same size among testing. ![]() So at least next two are required usually when observation, in addition to test with new profile(no extention) and test with newest trunk. > have had Seamonkey crash at using 180MB.īecause memory or resource management mechanism is different when bfcache, and because current memory cache size default is determined based on physical memory size, it is very difficult to check "whether memory leak is involved or not" by external obserbation of virtusl sotrage size only. > tab opened and closed after that increases the actual memory use, up to where I > But as soon as I close the tabs, the memory usage increases exponentially. (In reply to comment #0, in addition to my comment #6) O.V.Zenin, please be very carefull in using current "DOMLeak:5, DocumentLeak:5, nsDocShellLeak:5 and Leak Gauge tool combination" without termination, as leak detection tool. These are one of reasons why termination is required to use Leak Gauge tool. (because many many polling logs during idle are written by it. (This probably can be avoided by getting log of nsSocketTransport:5 same time) In addition to it, NSPR log data is probably buffered, then log for destroy object can be kept in buffer when you run Leak Gauge tool. (Including similarity to "garbage collector is not invoked just after destory object".) Increase from 6 at (a) to 10 at (c) is suspectable as a result of leak of something.īut destorying object is not always done just after Tab/Window close. > Upon closing all tabs/windows except for the one with about:blank : > Upon opening multiple tabs and windows: > Immediately after start with about:blank : But if VS4 is not so larger than VS2, it indicates that virual memory is re-used(usually heap is not freemain'ed but re-used), then no large memory leak is involved, and increase from VS1 to VS3 is guessed as simpley a result of other issue such as bug 130157, as Andrew Schultz says. If VS4>VS2, and if virual storage size largely increases on every step (6), memory leak is suspectable. Will virtual storage size increase infinitely? ![]() (5) VS5 : Close multiple tabs and windws ( same as step(3) ) (4) VS4 : Open multiple tabs and windws ( same as spep(2) ) What happens on virtual sotrage size when next steps are executed? Same question as Bug 327418 Comment #14 : > (3) VS3 : Upon closing all tabs/windows except for the one with about:blank : > (2) VS2 : Upon opening multiple tabs and windows: > (1) VS1 : Immediately after start with about:blank : You are saying that virtual storage is not freed(not returned to OS) after step (3), and suspecting "memory leak". OS: GNU/Linux, 2.4.29, glibc-2.3.6 (the same behavior is observed on _any_ linux system) Immediately after start with about:blank : Statistics of VM usage/object leak during the seamonkey session is as follows: > browser still running, and see if it reports only a couple leaks then, or a lot Could you run the leak gauge tool after closing all but one tab, but with the
0 Comments
Leave a Reply. |