#159 crash every few hours when I'm not looking

OBSOLETE_(1.11.x)
closed-invalid
nobody
crash (36)
5
2011-08-09
2011-08-05
Anonymous
No

Pidgin, using sipe, crashes every few hours. Months ago, with different versions of various components, it didn't do that. After days or weeks of crashes I started running Pidgin under "supervise" from D.J. Bernstein's daemontools.

Today I got my first Bug Buddy backtrace of the crash. I have installed the additional debuginfo as the backtrace suggests, in case the current backtrace is not good enough. I run openSUSE 11.4 x86_64.

Discussion

  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2011-08-05

    Bug Buddy backtrace of pidgin-sipe crash

     
  • Stefan Becker

    Stefan Becker - 2011-08-05

    While the backtrace shows some problem in sipe.c:4698, this is unfortunately not enough or incorrect information

    - what version of pidgin-sipe is installed? You selected version 1.11.2, but I can't match up the line numbers reported in the backtrace with sipe.c from the 1.11.2 release.
    - we need the output from "pidgin --debug" (i.e. we can see the message that triggers the problem)

    I would suggest to fetch the latest source code from git HEAD, compile & install it, and try to reproduce the problem with it. Then attach the latest backtrace and --debug log file to this report,

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2011-08-05

    2nd Bug Buddy backtrace of pidgin-sipe crash

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2011-08-05

    It's openSUSE pidgin-sipe 1.11.2-3.1 from repo http://download.opensuse.org/distribution/11.4/repo/oss/ for what that's worth. Sources are in pidgin-sipe-debugsource 1.11.2-3.1 which has line 4698 "sipe_process_imdn(sipe_private, msg);". I'm attaching that copy of sipe.c in case it helps.

    I'll look for the pidgin --debug output. I have modified my pidgin run script for daemontools to the following:

    exec /usr/bin/pidgin --debug >> $HOME/bin/pidgin_run/debug.out

    Thanks.

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2011-08-05

    http://download.opensuse.org/distribution/11.4/repo/oss/ pidgin-sipe-debugsource 1.11.2-3.1 sipe.c

     
  • Stefan Becker

    Stefan Becker - 2011-08-05

    There must be something wrong with your installation. Yes, sipe.c from 1.11.2 has in line 4698 sipe_process_imdn(), but that function is not mentioned in the backtrace. Also the other lines listed from sipe.c don't match up, i.e. there is no function calls in them down to the next level shown on the call stack.

    OR: I'm afraid you are hunting a corruption bug which just happens to point at pidgin-sipe.

    Please make sure to compile git HEAD and try to reproduce the problem with that one.

    The other test is to disable *ONLY* your pidgin-sipe account to see if the problem is still there or not. If it is still there and the backtrace still points to pidgin-sipe, then it is definitely a corruption from something else, because in this setup pidgin only loads the library and doesn't run anything beyond the init code.

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2011-08-09

    Thanks for the advice to use the debug output. Here's the "punchline" (at least, it made me laugh):

    (17:56:14) plugins: Not loading /usr/lib64/purple-2/libsipe.so. Another plugin with the same name (/usr/lib64/pidgin/libsipe.so) has already been loaded.

    Using 'strings' I confirmed that version 1.6.3 that I once put in with "make install" is getting loaded instead of version 1.11.2 that I more recently installed via "yast2". I suppose I'll go back to that old source directory, run "make -n install", and see what else I may need to get rid of.

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2011-08-09
    • status: open --> open-invalid
     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2011-08-09
    • status: open-invalid --> closed-invalid
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks