[2.0 beta3] Crash when receiving transferred file

[Andrew Conkling]

Binary package hint: gaim

My buddy wanted to send me a screenshot over Jabber, but it consistently crashed Gaim. The CPU would shoot up to 100% first.

I will attach a backtrace from the core file that was dumped.

[Sebastien Bacher (seb128)]

Confirmed on edgy with gaim 2.0beta3.1

[Andrew Conkling (andrewski)]

(I should've said before that I was on Edgy.)

A bit more info:
Sender (friend) and recipient (me) were each on Gaim on Edgy.
When sending my friend a file, he noticed the CPU spike, but cancelled the transfer with no repercussions.
He also tested receiving a file from someone over Oscar/AIM who was using AOL's IM client. He had no problems receiving the transfer.

I will do some further testing to try to narrow down what specifically causes this problem.

[Andrew Conkling (andrewski)]

So it would seem that AIM transfers do not cause this crash.

[Jeff Greene (jeffgreene)]

I crash on Edgy in beta 2.0 beta3 when using AIM, so I think this crash affects everything.

[Andrew Conkling (andrewski)]

On 9/23/06, Jeff Greene <email address hidden> wrote:
> I crash on Edgy in beta 2.0 beta3 when using AIM, so I think this crash
> affects everything.

Do you have gaim-dbg installed?

[Jeff Greene (jeffgreene)]

No, would you like me to install gaim-dbg and test it and send you the output?

[Andrew Conkling (andrewski)]

Yes, it would make your crash report more useful (though not to me ;).

[Jeff Greene (jeffgreene)]

Gaim has segfaulted and attempted to dump a core file.
This is a bug in the software and has happened through
no fault of your own.

If you can reproduce the crash, please notify the gaim
developers by reporting a bug at
http://gaim.sourceforge.net/bug.php

Please make sure to specify what you were doing at the time
and post the backtrace from the core file. If you do not know
how to get the backtrace, please read the instructions at
http://gaim.sourceforge.net/gdb.php

If you need further assistance, please IM either SeanEgn or
LSchiere (via AIM). Contact information for Sean and Luke
on other protocols is at
http://gaim.sourceforge.net/contactinfo.php
Aborted (core dumped)

[Jeff Greene (jeffgreene)]

Now when it crashes, I don't get the bug buddy thing to come up. How do I find the core dump?

[Jeff Greene (jeffgreene)]

Ok, I found out how it happens. It works if I accept the message within 5-10 seconds, but if I leave the accept dialog up for too long, it crashes gaim.

[Jeff Greene (jeffgreene)]

Attached is a crash log when running it in debug mode.
To repeat the steps for the crash:
1. Ask someone to send you a file.
2. When the file accept/cancel window comes up, just leave it there for 5-10 seconds.
3. Watch it crash.

Note: I am running this on Edgy Knot 3 with gaim 2.0 beta3.1, but I know it failed in Dapper and I think Windows too.

[Jeff Greene (jeffgreene)]

Attached is a backtrace doing the same steps.

[Mark Doliner (thekingant)]

My hope is that this will be fixed in beta 4. A lot of the code relating to this crash has been rewriting and is now a million times cleaner.

[Sebastien Bacher (seb128)]

Another backtrace from edgy on jabber file receiving:

"(gdb) bt
#0 0x00002ab4c1eeb0fb in __write_nocancel () from /lib/libpthread.so.0
#1 0x0000000000456f03 in proxy_do_write (data=0xcdd980, source=11,
    cond=<value optimized out>) at ../../src/proxy.c:1061
#2 0x000000000045707c in s5_canwrite (data=0xcdd980, source=11,
    cond=<value optimized out>) at ../../src/proxy.c:2134
#3 0x00000000004ae6cf in gaim_gtk_io_invoke (source=<value optimized out>,
    condition=<value optimized out>, data=<value optimized out>)
    at ../../src/gtkeventloop.c:74
#4 0x00002ab4c1b40d44 in g_main_context_dispatch ()
   from /usr/lib/libglib-2.0.so.0
#5 0x00002ab4c1b43b8d in g_main_context_check ()
   from /usr/lib/libglib-2.0.so.0
#6 0x00002ab4c1b43e9a in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#7 0x00002ab4c0de82e3 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0"

[Pete Savage (petesavage)]

This is still a problem for me, has there been any progress?

[Mark Doliner (thekingant)]

Have you tried with beta 5? I think it's in Ubuntu now. Maybe.

[Andrew Conkling (andrewski)]

On 11/15/06, Mark Doliner <email address hidden> wrote:
> Have you tried with beta 5? I think it's in Ubuntu now. Maybe.

No, not yet, unfortunately. There are some packages floating around the forums, though they have some problems: http://www.ubuntuforums.org/showpost.php?p=1742285&postcount=4.

[Andrew Conkling (andrewski)]

Thank you (self) for taking the time to report this bug and helping to make Ubuntu better. You (self) reported this bug a while ago and there hasn't been any activity in it recently. (The royal) we were wondering if this is still an issue for you(rself)? Can you (self) try with latest Ubuntu release? Thanks (self) in advance.

All of that is to say I haven't had this trouble lately, when I've had occasion to try a file transfer. The upstream bug seems to have disappeared too. Can anyone else confirm whether this is still a problem?

[Connor Imes (ckimes)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!