QtWeb
Internet Browser
QtWeb off-line Knowledge Base

 

Mem Usage

Author Topic: Mem Usage  (Read 393 times)

hwan
« on: March 28, 2009, 09:48:46 PM »

I mentioned this briefly in the "CPU load to high" thread.

When I start Qt, it uses about 30-35k in memory. Pretty soon, the number starts cascading higher. Occassionally it settles back down, but it usually ends up using more memory than Firefox! Earlier tonight I had 2 tabs open, one on the Wizards.com forums and one on cracked.com, and the browser usage was hovering somewhere around 150k. To compound the problem, the momry usage doesn't seem to want to deflate if I close a tab or two. If I have a single tab open, open another tab, then close one of them, the memory usage stays consistent.  Any thoughts/ideas/suggestions? This wouldn't be a problem on my home computer, but I'm on a work machine that is an absolute dinosaur.
 
NSFWStick
« Reply #1 on: April 04, 2009, 10:58:39 AM »

Perhaps QtWeb suffers from the same kind of memory problems Firefox does?

Or maybe someone forgot to do a memfree() somewhere...
 
Alex
« Reply #2 on: April 07, 2009, 12:37:41 PM »

Yes, unfortunatelly problem with memory usage exists in Qt 4.5.0 adaptation of WebKit implemenation Sad

I've found couple places, for example, in  FontCacheQt.cpp, which is not fully implemented.
However to dig through all 85MB of source code is too much.

Hopefully, in next releases of Qt,  developers will address this issue...
 
Alex
« Reply #3 on: April 14, 2009, 07:03:13 AM »

Hi

Fully rewritten Nokia's Qt 4.5.0 implementation of FontCache which was just not fully implemented.

QtWeb 2.0 build 051 contains custom implementation of FontCache.

Now browser has much less memory leaks

Details: http://code.google.com/p/qtweb/issues/detail?id=82&can=1
 
Michael
 
« Reply #4 on: April 14, 2009, 09:24:52 AM »

Awesome job, Alex, you're the man. QtWeb version is 2.0 (build 051) now runs smoothly with my laptop thanks to this new build.
 
hwan
« Reply #5 on: April 26, 2009, 05:46:31 PM »

Wow...wonderful. Yeh, it works great now.  Grin
 

Back to KB