Hi, might be a problem with the garbage collector (GC). Recently I helped a guy, who experienced heavy leaking on linux-64 with QtWebKit. It turned out later that the GC cannot detect unreferenced objects, and mmaping new pages again and again (~512k for each page). Sometimes the same thing happens on linux-32 as well: he said 1 out of 10 times he saw the same memory growing.
Zoltan > Hey, > > I have a tip... During my measurements with custom allocators (blog: > http://webkit.sed.hu/taxonomy/term/3), I experienced that running of js > benchmarks (SunSpider, V8, WindScorpion) in JS workers caused that > QtLauncher > consumed extraordinary amount of memory... > Wave is based on a lot of JavaScript and might use workers. Probably the > memory increasing comes from this region. This needs further > investigation. > > Regards, > > Zoltan > > On Thursday 25 March 2010, at 21:42, Heinz Wiesinger wrote: >> Hi! >> >> I discovered that the QtWebKit based browsers I use (arora, rekonq) seem >> to >> have a huge memory leak on wave.google.com. Memory usage increases by >> approx. 700MB after going to the start page (not the login page, the one >> where you actually see your "waves"). I'm using QtWebKit as of Qt 4.6.1, >> so maybe it was fixed in a newer version, but I am unable to test those >> right now. Has someone made similar experiences with google wave? Does >> this still happen with newer versions of QtWebKit? >> >> Grs, >> Heinz > _______________________________________________ > webkit-qt mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
