Bug 115598

Created attachment 49067 [details]
back trace of kontact crash

I don't understand why this was changed to major when the definition of critical
is as follows:

Critical  	Crash, loss of data, corruption of data, severe memory leak

This is a crash and should therefore be critical.

Created attachment 49072 [details]
another back trace

Here is another back trace on the same problem. Look similar.

and you don't ues news (nntp/knode) at all? because thats where it crashes 
 
 

(In reply to comment #4)
> and you don't ues news (nntp/knode) at all? because thats where it crashes 

Yes I do use Knode/nntp. I was just assuming that it was knode because it said
knode crash at the top of the backtrace screen, and I was in the mail view of
kontact at the time of the crash.

(In reply to comment #5)
> (In reply to comment #4)
> > and you don't ues news (nntp/knode) at all? because thats where it crashes 
> 
> Yes I do use Knode/nntp. I was just assuming that it was knode because it said
> knode crash at the top of the backtrace screen, and I was in the mail view of
> kontact at the time of the crash.
> 

I mean kontact crash not knode :) Regardless, I do use knode.

ok.. but kontact disappears, or knode? 
 
because to me it looks like knode crashes while kontact might or might not be 
running.  
 
 

(In reply to comment #7)
> ok.. but kontact disappears, or knode? 

Yeah, the whole kontact application disappears. But knode is running inside of
kontact as my news component. I am not running it outside of kontact as a
seperate application.

looks easy to fix 
 
#4  KPIM::ProgressItem::setProgress (this=0x0, v=0) at progressmanager.cpp:103  
#5  0x437d012b in KNNetAccess::slotThreadSignal (this=0x9403f38, i=24)  
    at knnetaccess.cpp:434  

its just one place, if you fix that one it will crash one line later.  

Joe: I assume you have interval news checking turned on in knode (Configure 
KNode->Accounts->Newsgroup Servers->[Account name]) and it is crashing while 
just sitting open due to an interval check happening? 

(In reply to comment #11)
> Joe: I assume you have interval news checking turned on in knode (Configure 
> KNode->Accounts->Newsgroup Servers->[Account name]) and it is crashing while 
> just sitting open due to an interval check happening? 

I do have the truned on and it checks every 5 minutes. If it is crashing on
that, then it only did it twice so far, and it is working the rest of the time.
Perhaps it is something that happens at the same time a the interval check?

Have applied a workaround that checks the ProgressItem is valid before trying  
to update it, which should prevent the crash.  I've asked the knode maintainer 
if he can untangle his threads, and if there's a proper fix I'll apply this to 
the next KDE update. 

I am still seeing this crash on almost a daily basis. I am running RC4. This
time I am just running Knode outside of Kontact, so I do know that it is knode
that is crashing.

Created attachment 51094 [details]
knode crash while sitting open

let me know if this ends up being a different issue. If it is, I will open a
new bug, but the symptoms are the same.

I have an update on this. I use evolution quite a bit because I typically run in GNOME. Therefore I run knode outside of kontact. This is when knode seems to crash. If I run Kontact for my email and am running knode within kontact, I don't see the crash. Or at least I haven't seen it yet.

ok, next try: please try 10.1 - knode works fine for me, and Volker fixed quite some bugs for 3.5 (which is about the only knode development happening atm).

if you can still reproduce it: let knode run through valgrind - it must be something specific to your settings

(In reply to comment #17)
> ok, next try: please try 10.1 - knode works fine for me, and Volker fixed quite
> some bugs for 3.5 (which is about the only knode development happening atm).
> 
> if you can still reproduce it: let knode run through valgrind - it must be
> something specific to your settings


No problem, sounds good. I will let you know if I find anything with 10.1 beta 4.