Are you able to reproduce this reliably? Are you using http method?

There's a git branch 'sb-cleanups' that might fix the issue, can you try that?

The PPA package is uploaded to sb-cleanups branch.

It still occurs often with the latest package of pecan and of Pidgin

I don't know how to reproduce it, though it happens quite frequently. I'll try to see
if i can reproduce it though.

BTW, did you disable all plugins, protocols and smiley packs etc.?  I had a smiley
pack a while ago that kept crashing my MSN in Pidgin, so it could be something else
being triggered by WLM, just a thought.

I have all of the smiley packs and protocols disabled. Not the plugins, but the
tracebacks would have said it was a plugin

I've recognized, that msn-pecan crashes, when a current conversation is openened, but
my chatpartner gets disconnected from the msn network.

It only happens with active conversations, when other buddys (i do not talk to
currently) from my list sign off, nothing crashes.

Maybe this is helpful. I noticed it after opening the last logs from these
conversations after the crash. Most time the chatpartners had been disconnected at
the time of the crash.

schmatzler: thanks, that helps.

From: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528231

(gdb) handle SIGPIPE noprint nostop
Signal        Stop	Print	Pass to program	Description
SIGPIPE       No	No	Yes		Broken pipe
(gdb) r
Starting program: /usr/bin/pidgin 
[Thread debugging using libthread_db enabled]
[New Thread 0xb6fe4750 (LWP 11527)]
warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6fe4750 (LWP 11527)]
0xb77ec40e in g_hash_table_destroy () from /usr/lib/libglib-2.0.so.0
(gdb) bt
#0  0xb77ec40e in g_hash_table_destroy () from /usr/lib/libglib-2.0.so.0
#1  0xb5634dd8 in msn_message_destroy (msg=0xac79630) at cmd/msg.c:86
#2  0xb5634eb6 in msn_message_unref (msg=0x0) at cmd/msg.c:142
#3  0xb5634dc8 in msn_message_destroy (msg=0xac79630) at cmd/msg.c:65
#4  0xb562406b in send_typing (gc=0x948b930, who=0xa8b92b8 "OBFUSCATED@SERVER",
state=PURPLE_TYPING) at 
msn.c:1098
#5  0xb77528ea in serv_send_typing (gc=0x948b930, name=0xa8b92b8 "OBFUSCATED@SERVER",
state=PURPLE_TYPING)
    at ../../libpurple/server.c:57
#6  0x08097b26 in got_typing_keypress (gtkconv=<value optimized out>, first=<value
optimized out>)
    at ../../pidgin/gtkconv.c:3539
#7  0xb7aec1ca in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#8  0x0a8c6520 in ?? ()
#9  0xbffda0a4 in ?? ()
#10 0x0a3f8c88 in ?? ()
#11 0x00000001 in ?? ()
#12 0x0a5f7878 in ?? ()
#13 0x0a43ed18 in ?? ()
#14 0x0a8c6520 in ?? ()
#15 0xb78b2680 in ?? () from /usr/lib/libgobject-2.0.so.0
#16 0x0a955d48 in ?? ()
#17 0x00000000 in ?? ()
(gdb) 

 Issue 125  has been merged into this issue.

 Issue 122  has been merged into this issue.

I just pushed a fix to git master that might fix this problem. Anyone willing to test?

I was affected by this crash, and I've updated my msn-pecan library to the latest git
version. I'll let you know if pidgin is still crashing. Thank you!

frasten: please make sure you use b1a4a7c, I think I introduced a regression yesterday 
and the latest commit fixes it (probably).

Ok, I was using g3f40aeb, but I've updated it now.

Good news, it hasn't crashed yet (but I'll keep testing). Good job! :-)

yay \o/

Marking as fixed.

Can someone verify this is fixed on 0.0.19?

I haven't seen this crash anymore, since the last commits to the git repository,
thank you.

Marking as verified, thanks guys :)