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

List:       kde-bugs-dist
Subject:    Bug#33240: Kmail crashes randomly, normally when idle
From:       Nick Lawes <nick () grok ! demon ! co ! uk>
Date:       2001-10-03 22:13:43
[Download RAW message or body]

On Wednesday 03 Oct 2001 09:33, you wrote:
> On Wednesday 03 October 2001 03:15, nick@grok.demon.co.uk wrote:
> > Periodically kmail crashes with a backtrace. This happens fairly
> > regularly, and has been doing so since I installed KDE 2.2. I was
> > hoping that KDE 2.2.1 (kmail 1.3.1) would fix the problem. Since
> > it's only been installed for a couple of hours, and it's crashed
> > already, I assume it's not fixed.
>
> Well, as usual backtraces generated from an RPM installation are not
> as informative as possible.
> Eventually this looks like some memory got corrupted. Some days ago,
> I indeed fixed something, that could cause this, but I don't know if
> that is your problem. You could just update KMail from the
> KDE_2_2_BRANCH on any CVS mirror and see, if this fixes it.

Okay, I will pick up the latest kmail source and recompile it. I am 
running against SuSE install, updated with the suse rpms for kde 2.2 / 
qt 2.3.1, then updated with the kde 2.2.1 (no qt, and no noarch as the 
directory was empty).

So, is the 2.2 supplied qt-2.3.1 okay, or would you recommend 
rebuilding that as well? Presumably it, and the kde libs should be 
okay, and hopefully contain debug symbols.

I could then run it from gdb I guess to get a better chance to poke 
around, if that would be useful, or will the stack trace be enough?

> If you click trough all folders, does it crash when selecting a
> special folder?

I can happily click on all the folders.

> Does it also crash, if you disable interval mailchecking and check
> your mails only manually?

It doesn't happen frequently enough to know that one for sure, so it 
may be best to leave that test until second... I can always switch my 
mail pickup to use fetchmail and biff, then collect the mail in kmail 
from a local pop box, or I could knock up a biff-type ISP mailbox 
checker using scripts and programs I have lying around, and pick up the 
mail from the ISP when I know it's there. While this may cure my 
immediate problems, it probably won't help isolate the real cause. I 
think it would be better to try to find the problem if possible. I know 
that a couple of my colleagues at work see similar problems, so I don't 
think it's just me.

FYI I tend to leave kmail running 24/7, if this makes a difference. I 
do the same at work, and do see similar problems there. I'll rebuild 
kmail from source at work too. Crashes vary between, say, a couple in 
one day (rare), to one every few days. 

Funnily enough it just "locked up" on me without a stack trace, while I 
was typing in this message, I'd received another mail message, replied 
to it, and hit send from the composer. All windows stopped updating. I 
left it for 10 minutes, then killed it.

Recovery mode worked beautifully, both my edit windows came up, intact, 
and the send that time succeeded.

> Regards,
> Michael Hckel

Regards

/nick

-- 
Nick Lawes | mailto:nick@grok.demon.co.uk

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