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

List:       sylpheed
Subject:    [sylpheed:25026] Re: 1.9.12 crash
From:       Hiroyuki Yamamoto <hiro-y () kcn ! ne ! jp>
Date:       2005-05-31 6:43:55
Message-ID: 20050531154355.4dbaa8f6.hiro-y () kcn ! ne ! jp
[Download RAW message or body]

Hello,

On Mon, 30 May 2005 19:22:45 +0200
Yann Grossel <sylpheed@yg.noc.fr.clara.net> wrote:

> More info from my coredump :
> 
> Core was generated by `/opt/bin/sylpheed'.
> Program terminated with signal 11, Segmentation fault.
> ...
> (gdb) frame 1
> #1  0x08073704 in summary_show (summaryview=0x823ae40,
> #item=0x82d9880, update_cache=0) at summaryview.c:593
> 593             summaryview->folderview->opened =
> (gdb) p summaryview
> $1 = (SummaryView *) 0x823ae40
> (gdb) p summaryview->folderview
> $2 = (FolderView *) 0x821c188
> (gdb) p summaryview->folderview->opened
> $3 = (GtkTreeRowReference *) 0x82d7a60
> (gdb) p summaryview->folderview->selected
> $4 = (GtkTreeRowReference *) 0x0
> 
> It seems than in some circunstances (unknown for now), the "selected"
> field of the summaryvieuw->folderview is unexpectedly NULL, and of
> course that makes the gtk_tree_row_reference_copy() call to segfault.
> 
> My always-running Sylpheed is connected to an IMAP server with lots of
> (open) folders. I configured Sylpheed to "check for new mail" every 1
> minute. New mails are therefore receveid regularly in various folders.
> 
> One can suspect that the crash occurs when new mails arrive in
> specific folders (maybe the folder currently selected ? I didn't had
> time make some tests for now). 

I don't know why selected becomes NULL at the timing, but I've made a
workaround for it at the svn trunk.

-- 
Hiroyuki Yamamoto <hiro-y@kcn.ne.jp>

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