[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:21:55
Message-ID: 20050210062155.5680.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:21 -------
Thanks for your note.  A couple notes below:

On Tuesday 08 February 2005 03:01 am, Carsten Burghardt 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
>
>
>
>
> ------- Additional Comments From burghardt kde org  2005-02-08 09:01
> -------
>
> > Carsten,
> >
> >    I appreciate that this issue is not BECAUSE OF kmail.  But as a
> > programmer (32 years) and software developer I thought your team might
> > find this information of interest.  Certainly if folks are complaining
> > about kmail, and other KDE apps having memory leaks, due to this problem
> > is is in some way RELATED. It's *your program* that crashes because of
> > this!!!!
>
> Yes but there is nothing we can do in kmail to work around this as it
> obviously affects kde in general.

OK.  I just had to pick an app because there is no "General KDE" choice in the 
bug reporting page.  It's as if there could not be a bug that affected KDE in 
general......  Not your fault, or mine....

>
> >    Or perhaps you would have preferred to have been left in ignorance
> > about a very real problem that affects your products, and makes them
> > look bad when it is probably not your fault.  At least now you know
> > who/what to blame.  Two days ago, your team denied a problem
> > existed......  It does exist.  Whether you contact the folks that make
> > the WASP icon set, or your [seemingly broken] SVG handler, is up to you.
>
> Then why don't you contact these folks yourself if know that their iconset
> is buggy? You could have reported this bug against kdelibs but even then
> it's the task of the creators of this iconset if I understand you
> correctly. Not that I haver ever seen WASP.
>
> >    Sorry if you feel I wasted your time.  I will not do so in future.
>
> That's not the point. We're thankful for every useful bug report but this
> is definitely not a problem that kmail can address.

OK Carsten.  That's entirely your call.  I had just assumed someone like you 
might be in a much better position to know who to route this thing to than 
me.  The KDE bug report page requires that a specific app be targeted, so I 
chose the app that had been the most troublesome to me, and most frequent - 
figuring that the bug replication would be certain for kmail, although the 
bug has affected several KDE apps.

Just install the WASP icon set, bring up kmail or krusader, work with them for 
a few minutes, and you should see all yuour memory "eaten" and a core dump 
file equal to your system memory and swap space produced.

My goal was to let KDE know how to easily replicate the fault, not pick on the 
email app I use, and have used for years, the very most!

Thanks for your reply.  If I can help you find this thing, don't hesitate to 
call (706-769-69245) or email.  I'm retired, so I don't mind. 

It's an odd bug, and I used to do what you do now, so I am just trying to 
provide what info I can to help.

Terry


>
>
> Carsten
[prev in list] [next in list] [prev in thread] [next in thread]