Opened 9 years ago

Last modified 5 years ago

#8467 new defect

Crash on solaris when message received

Reported by: flynd Owned by: EionRobb
Milestone: Component: unclassified
Version: 2.5.4 Keywords:


Sometimes when I receive a message, Pidgin crashes. Message is written to log and sound is played for event before crash occures. I have only seen this behaviour when receiving messages for a user when the window is already open. Several of the times I was writing a message in the same or another pidgin window at the time of the crash. I only use meanwhile protocol.

I previously used version 2.3.1 and did not experience any crashes with that version.

I searched for other tickets and found #6619 which could be the same problem, however it was closed due to no stack trace.

System type: SunOS sekasr-sol-1 5.10 Generic_127127-11 sun4u sparc SUNW,SPARC-Enterprise

Configure command used: ./configure --prefix=/opt/local/user/kde-3.5.10 --disable-doxygen --disable-gtkspell --disable-gstreamer --disable-avahi --disable-dbus --disable-perl --disable-tcl --disable-gnutls

I will attach a backtrace.

Attachments (2)

pidgin-2.5.4-crash (6.1 KB) - added by flynd 9 years ago.
Backtrace of a crash
pidgin-2.5.8-crash (5.9 KB) - added by flynd 9 years ago.
Backtrace from Pidgin 2.5.8

Download all attachments as: .zip

Change History (16)

Changed 9 years ago by flynd

Backtrace of a crash

comment:1 Changed 9 years ago by flynd

Is there any chance of getting this fixed? It's very annoying having Pidgin crash several times per day. A rough estimate is that it has a 10% chance of crashing when I receive a message if I have the message window already open for that user. It doesn't seem to matter if the window is in focus but I think it's more likely to happen if I'm currently typing a message to the user.

If you need any more information, just let me know and I'll provide it.

comment:2 Changed 9 years ago by deryni

  • Status changed from new to pending

This is crashing deep inside GTK+ (with a pit stop in the pidgin gtkimhtml widget), unfortunately that makes this harder to figure out. What version of GTK+ are you using? Where did you get it from? Where did you get pidgin from?

You said pidgin 2.3.1 was working, did you upgrade GTK+ around the time you upgraded pidgin to 2.5.4?

comment:3 Changed 9 years ago by flynd

  • Status changed from pending to new

I built Pidgin 2.5.4 directly from source. I used a sparc/solaris machine and compiled just the minimum needed get Pidgin (and a few other things like KDE) running on that system. I'm using GTK+ version 2.4.9 as this is what's included in Solaris 10 and I wanted to build as few dependancies as possible myself. (Solaris 10 actually contains Gaim 1.5.0 as well but I thought it would be worth getting something newer to use.)
The things I did compile myself for Pidgin was GetText? (0.17) and Meanwhile (1.0.2). I've also compiled Pcre (7.8), Cups (1.3.9), GMP (4.2.4) and Qt (3.3.8) as dependancies for KDE (3.5.10). Everything else on the system are the default versions shipped with Solaris 10 8/07. I also skipped some dependancies that I didn't bother to find or build, the configure parameters are listed in the ticket description above and shows my disable parameters.

The previous setup with Pidgin 2.3.1 was installed precompiled from together with a bunch of other packages. I'm not sure but I would guess GTK+ was also taken from there. I don't know which version I was using but latest available version today is 2.12.3.

The reason for all this is my environment at work. On my previous workstation I could use the blastwave packages, but on my new workstatien I don't have the possibility to install packages myself, so I've compiled what I needed and placed in a writable directory. Due to the work environment being littered with old or broken libraries in various odd directories I didn't want the configure scripts to find, I did all the compiling on another maching with just a clean Solaris 10 installation on. The Solaris libraries and paths are the same and ldd shows that Pidgin will use the correct libraries on my workstation as well.

comment:4 Changed 9 years ago by deryni

  • Status changed from new to pending

It might be informative for you to try compiling and installing pidgin 2.3.1 the same way you did 2.5.4 to see if that also crashes.

I have a feeling this may be a GTK+ bug (which assuming the older blastwave package did in fact use the newer blastwave GTK+ package would have avoided).

Trying the same version of pidgin should (hopefully) let you find out whether the version of pidgin is the issue (if it crashes you will know pidgin isn't the issue, if it doesn't crash you won't know pidgin is unfortunately).

comment:5 Changed 9 years ago by flynd

  • Status changed from pending to new

I've compiled Pidgin 2.3.1 but with everything else the same version as before. I haven't seen any crashes today but I haven't used it much today and the crashes are not predictable (sometimes several times per day and sometimes only a few times per week) so it's too early to tell. I'll continue to use 2.3.1 and see what happens...

comment:6 Changed 9 years ago by flynd

I've used the 2.3.1 version for a week now without seeing any crashes. I've chatted with the same people that was causing the crashes with 2.5.4 so most probably there is no problem when using 2.3.1.

I recompiled only Pidgin from 2.3.1 sources, everything else is the same as when 2.5.4 was crashing. The same libraries are available and the configure parameters was used.

comment:7 Changed 9 years ago by flynd

Today I tried to version 2.4.3 and it also crashed. I didn't check the backtrace but I assume that it was the same fault.

comment:8 Changed 9 years ago by flynd

Crashed with 2.4.0 as well. So 2.3.1 seems to be latest version without the problem.

comment:9 Changed 9 years ago by QuLogic

  • Owner changed from lschiere to rekkanoryo

comment:10 Changed 9 years ago by bernmeister

flynd: Are you still experiencing this issue with 2.5.8?

comment:11 Changed 9 years ago by QuLogic

  • Status changed from new to pending

comment:12 Changed 9 years ago by flynd

  • Status changed from pending to new

I'll build 2.5.8 and see if it still crashes. However I cannot do that right now since I only have the Solaris environment at work and I'm currently on vacation for another 3 weeks.

I'll update this ticket again with the result sometime next month when I'm able to try it. Please don't autoclose the ticket while waiting.

comment:13 Changed 9 years ago by flynd

Crash reproduced with 2.5.8 as well.

Changed 9 years ago by flynd

Backtrace from Pidgin 2.5.8

comment:14 Changed 5 years ago by rekkanoryo

  • Owner changed from rekkanoryo to EionRobb
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!