Bug 51370

Summary: memory leak viewing http://www.cambridge-news.co.uk/
Product: [Applications] konqueror Reporter: cb-kde
Component: kjsAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: esigra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description cb-kde 2002-11-30 20:43:48 UTC
Version:           unknown (using KDE 3.0.9)
Compiler:          gcc version 2.95.4 20011002 (Debian prerelease)
OS:          Linux (i686) release 2.5.47

To reproduce:

start KDE 3.1rc3. Load 2 xterms
in one, run top and sort by memory usage.
in the other type konqueror http://www.cambridge-news.co.uk/

Leave for some time. Observe that the memory usage (VIRT in top 3.1.0) has increased substantially.

This memory is not reclaimed if browsing continues to a different site.

Plugin support is disabled.

Expected behaviour:
Memory usage is constant once the page has been loaded.
Comment 1 Dirk Mueller 2002-12-02 03:35:28 UTC
no leak here. NVIDIA drivers ? old xfree? 
Comment 2 cb-kde 2002-12-02 14:38:14 UTC
Subject: Re:  memory leak viewing http://www.cambridge-news.co.uk/

On Monday 02 December 2002 2:35 am, Dirk Mueller wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=51370
> mueller@kde.org changed:
>
>            What    |Removed                     |Added
> -------------------------------------------------------------------------
>--- Status|UNCONFIRMED                 |RESOLVED
>          Resolution|                            |WORKSFORME
>
>
>
> ------- Additional Comments From mueller@kde.org  2002-12-02 03:35
> ------- no leak here. NVIDIA drivers ? old xfree?

Xfree86 4.2.1 no NVidia or other proprietry drivers.

I have reproduced your difficulty in reproducing this :)

I tried again this morning and the memory leak did not occur until I played 
with Konqueror a bit. I moved the windows around, selected and deselected 
text and hovered over the popup menus for a bit. Once I'd done that the 
memory leak behaviour started and Konqueror gradually increased its memory 
usage.

I then reloaded Konqueror, and found that the memory leak started straight 
away.

In order to help you reproduce what I'm doing, I describe what I've done in 
more detail.

X is 1024x768 with 16bit colour.
There are two xterms, one in the top left, one at the bottom right
The xterm in the top left runs top
Place the mouse in the top left of the bottom right xterm
type konqueror http://www.cambridge-news.co.uk/

I use Qt 3.1.0 using xft font rendering. Anti aliasing is enabled for all 
point sizes and not using sub-pixel rendering. Java and plugin support is 
disabled. I use the Light style 3rd revision.

It seems there's some sort of timing issue which triggers it. 

Comment 3 cb-kde 2002-12-04 11:03:35 UTC
Reopening, as I have supplied more detail on reproducing it. 
Comment 4 cb-kde 2003-11-15 10:46:26 UTC
Can't determine if this is fixed due to http://bugs.kde.org/show_bug.cgi?id=68262                                       
Comment 5 cb-kde 2003-12-03 21:41:20 UTC
Seems to have gone away...