Opened 10 years ago

Closed 10 years ago

#9145 closed defect

Crash on exit - 2.5.5 and 2.5.5-debug

Reported by: fkirchner Owned by: deryni
Milestone: Component: XMPP
Version: 2.5.5 Keywords:
Cc: arrwrr

Description

Crash on exit. Happens whenever I exit pidgin. 2.5.5 and 2.5.5-debug.

Attachments (2)

pidgin.RPT (26.5 KB) - added by fkirchner 10 years ago.
rpt file
pidgin.2.RPT (38.7 KB) - added by arrwrr 10 years ago.
Arrwrr's crash dump

Download all attachments as: .zip

Change History (8)

Changed 10 years ago by fkirchner

rpt file

comment:1 follow-up: Changed 10 years ago by deryni

  • Status changed from new to pending

Does this only happen if you have chat windows open? If so this is probably #8774.

comment:2 in reply to: ↑ 1 Changed 10 years ago by arrwrr

Probably not. I have the same issue, also on a Vista system. "Program stopped responding" message pops up on ever single Exit. Regardless of opened windows or installed plugins.

Replying to deryni:

Does this only happen if you have chat windows open? If so this is probably #8774.

comment:3 Changed 10 years ago by arrwrr

The problem has something to do with services. Each services for itself (ICQ, jabber, irc, msn) works fine, but if you combine them, they can lead to crashes. I couldn't figure out any pattern. Whether a configuration of services causes a crash seems random. But once that crash has occured, it reoccurs on every single Exit.

Uploading rpt now.

Changed 10 years ago by arrwrr

Arrwrr's crash dump

comment:4 Changed 10 years ago by darkrain42

arrwrr, your crash is #8774.

comment:5 Changed 10 years ago by arrwrr

Oh, thanks for pointing that out. Sorry for not doing proper research on the topic. :(

comment:6 Changed 10 years ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!