Bug 471856 - Pidgin crash suddenly when typing something
Summary: Pidgin crash suddenly when typing something
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: pidgin
Version: 5.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Warren Togami
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On: 470000
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-17 07:44 UTC by Golita Yue
Modified: 2008-12-01 19:11 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-01 19:11:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Golita Yue 2008-11-17 07:44:36 UTC
+++ This bug was initially created as a clone of Bug #470000 +++

Description of problem:
Following are the info collected by bug-buddy:
-----------
System: Linux 2.6.27.4-68.fc10.i686 #1 SMP Thu Oct 30 00:49:42 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 2960982016 vsize: 2960982016 resident: 51773440 share: 24920064 rss: 51773440 rss_rlim: 18446744073709551615
CPU usage: start_time: 1225847969 rtime: 6704 utime: 5428 stime: 1276 cutime:15 cstime: 63 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/pidgin'

0x00110416 in __kernel_vsyscall ()
#0  0x00110416 in __kernel_vsyscall ()
#1  0x005ce777 in poll () from /lib/libc.so.6
#2  0x00727742 in ?? () from /lib/libglib-2.0.so.0
#3  0x00727dd2 in g_main_loop_run () from /lib/libglib-2.0.so.0
#4  0x058cc489 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#5  0x080c6b86 in main (argc=1, argv=0xbffdf884) at gtkmain.c:888
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
warning: difference appears to be caused by prelink, adjusting expectations
(firefox:7163): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox:7163): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox:7163): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox:7163): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox:7163): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox:7163): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
(firefox:7163): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------

Version-Release number of selected component (if applicable):
pidgin-2.5.2-1.fc10.i386

How reproducible:
1 / 10

Steps to Reproduce:
   set/unset Block function in Privacy
   send and receive messages
  
Actual results:
Pidgin often crash suddenly during above action. 

Expected results:
Pidgin does not crash

Additional info:

--- Additional comment from yzhou on 2008-11-05 02:24:31 EDT ---

Crash secondly:

--------
System: Linux 2.6.27.4-68.fc10.i686 #1 SMP Thu Oct 30 00:49:42 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 3026124800 vsize: 3026124800 resident: 54812672 share: 24596480 rss: 54812672 rss_rlim: 18446744073709551615
CPU usage: start_time: 1225867782 rtime: 2245 utime: 1917 stime: 328 cutime:4 cstime: 17 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/pidgin'

0x00110416 in __kernel_vsyscall ()
#0  0x00110416 in __kernel_vsyscall ()
#1  0x005ce777 in poll () from /lib/libc.so.6
#2  0x00727742 in ?? () from /lib/libglib-2.0.so.0
#3  0x00727dd2 in g_main_loop_run () from /lib/libglib-2.0.so.0
#4  0x058cc489 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#5  0x080c6b86 in main (argc=1, argv=0xbf92a9d4) at gtkmain.c:888
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
E: shm.c: mmap() failed: Cannot allocate memory
pidgin: pulse.c:203: pulse_new: Assertion `p->context' failed.
--------------------------------------------------

--- Additional comment from yzhou on 2008-11-05 04:25:35 EDT ---

It has crashed the third time, the same backtrace output with the second time.

--- Additional comment from stu on 2008-11-05 12:11:30 EDT ---

The backtrace doesn't show anything useful at all. Please install relevant debuginfo with "debuginfo-install pidgin".

> pidgin: pulse.c:203: pulse_new: Assertion `p->context' failed.

This looks like it may be crashing in pulse when trying to play a sound - if you disable sounds does it stop crashing?

Also what protocols and plugins do you use?

Comment 1 Golita Yue 2008-11-17 08:02:56 UTC
Version-Release number of selected component (if applicable):
pidgin-2.5.1-3.el5

Comment 2 Lawrence Lim 2008-11-17 17:07:14 UTC
Should this be fixed for 5.3?

Comment 3 Warren Togami 2008-11-23 19:20:33 UTC
llim, entirely unhelpful...

Comment 4 Warren Togami 2008-11-23 19:21:04 UTC
http://people.redhat.com/wtogami/temp/pidgin/
Please test these binaries.  Any better or different?

Comment 5 Golita Yue 2008-11-27 08:05:49 UTC
Test with all pidgin test cases, this error cannot be reproduced with pidgin 2.5.2-3.el5.1

Comment 6 Warren Togami 2008-12-01 19:11:46 UTC
The original bug had something to do with pulseaudio, RHEL5 has no pulseaudio.  Closing.


Note You need to log in before you can comment on or make changes to this bug.