XChat freezes during close when running for several hours - xchat crashed with SIGSEGV in Perl_pp_gvsv()

Bug #529342 reported by Vish
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xchat (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: xchat

Steps to reproduce:
1: start xchat
2: let xchat run continuously for several hours. [around 5-6 hrs min]
3: After several hours , Now close xchat.

Problem:
Xchat freezes and does not close
- it starts using high cpu and just remains

Workaround:
1: Disable/dont use the Auto-away plugin attached here
2: Force quit xchat.

This has been happening for over a month now , and i'm not sure which update this started with. But earlier [on lucid] it was working properly , this is a regression that I'm noticing.

I wasnt sure how to report this earlier, hence the delay.

To attain the crash report , I used $kill -11 <xchat PID>

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 6c350872f0b430ef8235c693ed2354c1
CheckboxSystem: 5484a8dd99f006173bd2ac53fa4837c2
Date: Sun Feb 28 11:52:14 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/xchat
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
Package: xchat 2.8.6-4ubuntu4
ProcCmdline: xchat
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
 Segfault happened at: 0x173b4d1 <Perl_pp_gvsv+65>: mov (%eax),%edi
 PC (0x0173b4d1) ok
 source "(%eax)" (0x09b99a68) ok
 destination "%edi" ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: xchat
StacktraceTop:
 Perl_pp_gvsv () from /usr/lib/libperl.so.5.10
 Perl_runops_standard () from /usr/lib/libperl.so.5.10
 Perl_call_sv () from /usr/lib/libperl.so.5.10
 ?? () from /usr/lib/xchat/plugins/perl.so
 xchat_plugin_deinit () from /usr/lib/xchat/plugins/perl.so
Title: xchat crashed with SIGSEGV in Perl_pp_gvsv()
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
SegvAnalysis:
 Segfault happened at: 0x173b4d1 <Perl_pp_gvsv+65>: mov (%eax),%edi
 PC (0x0173b4d1) ok
 source "(%eax)" (0x09b99a68) ok
 destination "%edi" ok
 SP (0xbfdc47d0) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

Revision history for this message
Vish (vish) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 Perl_pp_gvsv () from /usr/lib/libperl.so.5.10
 Perl_runops_standard () from /usr/lib/libperl.so.5.10
 Perl_call_sv () from /usr/lib/libperl.so.5.10
 execute_perl (function=<value optimized out>,
 xchat_plugin_deinit (plugin_handle=0x9a8baa8) at perl.c:1320

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xchat (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Vish (vish)
visibility: private → public
Revision history for this message
Vish (vish) wrote :

From my plugin and scripts list , there is a list of the default plugins , perl , tcl and python.

The extra plugin is X-away plugin , attaching the plugin and its conf files. [but i have not had any problems with this plugin earlier, been using the plugin for a long time]

Revision history for this message
Vish (vish) wrote :
Revision history for this message
Vish (vish) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

I tried recreating this bug on Lucid using xchat version 2.8.6-4ubuntu4. I exited xchat by going to XChat -> Quit and xchat closed without a problem. Is that how you quit it? Additionally, could you test it without the away plugin? Thanks in advance.

Changed in xchat (Ubuntu):
status: New → Incomplete
Revision history for this message
Vish (vish) wrote :

@Brian, Yes , i quit xchat similarly.
Yes , this problem is only when the Away plugin is activated. :( This started only recently in Lucid, I had been using this plugin for a long time.

PS: If you have an alternate auto-away plugin suggestion , we can close this bug ;-)

Changed in xchat (Ubuntu):
status: Incomplete → New
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

I was able to recreate this bug with that particular away plugin. I'm changing the importance to Low since it requires a specific plugin that is not installed by default.

Changed in xchat (Ubuntu):
importance: Medium → Low
status: New → Confirmed
Kees Cook (kees)
description: updated
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Vish, is it still an issue with lucid final and Maverick ?

Changed in xchat (Ubuntu):
status: Confirmed → Incomplete
tags: added: regression-release
Revision history for this message
Vish (vish) wrote :

jibel, i asked upstream xchat too about the away plugin , they seemed to think that the plugin is at fault.
So i stopped using the plugin and seems no one else is using the plugin either.

So closing this bug, we can probably focus on more important bugs ;-)

Changed in xchat (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.