[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 98753] Memory leak allocates until program crashes
From:       Terry Wilkinson <fudoki () bellsouth ! net>
Date:       2005-02-10 6:10:28
Message-ID: 20050210061028.321.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=98753         




------- Additional Comments From fudoki bellsouth net  2005-02-10 07:10 -------
Thanks for your kind response!

This is why I prefer KDE and help out with the Krusader Krew....

No, no - you have no bug in Kmail!! (as far as I can tell)

WASP is one of the Icon sets included with Mandrake and Redhat, and probably 
other distros.  It's based on the old BEOS "look and feel", a bright, yellow, 
black, and orange icon set.  Really nice contrast if you are old and your 
eyes are ruined from programming....

Since I am running mdk10.1 from RPM's, there are no debug symbols compiled in 
my apps.....  so no backtrace...  but I think the strace is adequate.

The "strace" output is the same for Krusader, Kmail, or other KDE apps.  
Something in the WASP icon set is broken and causes KDE to memory fault.  I 
think there is probably room for improvement on both sides of this 
equation....  but it appears the problem is some kind of file corruption or 
failure with the WASP icon set.  I bring this to *KDE's* attention because 
Gnome (and Gnome apps) seem immune.

Other Linus GUI's do not seem to be affected.

There is something about this icon set, notable the "find.svg" icon, that 
causes the memory crash I documented with my trace.  At least that's the icon 
being accessed when the memory gluttony occurs.... It's definitely an 
interaction with KDE.  But when WASP icons are not used, KDE runs flawlessly 
(for me, on all machines).

The trace was done by bringing up a terminal, and running the application with 
the "strace" tracer.  Syntax: strace -o <dump file path and name> <app name>

I lack the familiarity with KDE to determine where the problem is, but can 
show the cause.  Not using the WASP icon set eliminates the problem on any of 
my computers, running mdk 10 and 10.1.  Using the WASP icon set causes 
immediate memory leak crashes on any of my computers.

All my experience and instincts point to malformed files in the WASP icon set, 
or possibly a flawed input parse function in some of the KDE  graphics 
libraries that deal with fonts - but they seem to work so well everywhere 
else....

Have been a programmer for 32 years, now retired. If I can be of further 
assistance, don't hesitate to ask.

If this happened on one computer, it would obviously be a damaged file, but it 
occurs on different computers, running different versions of MDK.

This is one of those "weird" bugs that come up.  

Warm regards,

W. T. "Fudoki" Wilkinson

On Monday 07 February 2005 07:02 pm, Thiago Macieira wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=98753
> thiago.macieira kdemail net changed:
>
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
>- Product|kmail                       |kdelibs
>
>
>
> ------- Additional Comments From thiago.macieira kdemail net  2005-02-08
> 01:02 ------- Terry, can you provide a backtrace of the crash? The KDE
> crash handler seems to be opened, according to your strace.
>
> Please understand that the KMail team cannot solve the problems outside
> their influence. I, for one, have no idea what WASP is. I can tell you I
> have no file in my system with "wasp" in the name. What's more, your strace
> seems to be from krusader, not kmail.
>
> If there is a bug in our SVG rendering engine, we'll fix it.
[prev in list] [next in list] [prev in thread] [next in thread]