After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 332302 - Rhythmbox hangs/freezes when exiting
Rhythmbox hangs/freezes when exiting
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: general
0.9.3
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-23 10:47 UTC by Trygve Falch
Modified: 2006-09-28 13:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Trygve Falch 2006-02-23 10:47:12 UTC
Please describe the problem:
Quitting the application makes Rhythmbox non-responsive, requiring an explicit
KILL to quit the application.

The version I'm running;

0.9.3.1-0ubuntu1

which comes with Ubuntu Dapper, last updated 2006-02-23


Steps to reproduce:
1. Start Rhythmbox
2. Quit Rhythmbox (with or without music playing)
3. Observe the application freeze


Actual results:


Expected results:


Does this happen every time?
Yes

Other information:
This is a small part of the trace, right after I've tried to quit the application;

$> strace -f -p  11293

[pid 11293] futex(0x83ef730, FUTEX_WAIT, 2, NULL <unfinished ...>
[pid 11295] <... futex resumed> )       = -1 ETIMEDOUT (Connection timed out)
[pid 11295] futex(0x8323ac0, FUTEX_WAKE, 1) = 0
[pid 11295] gettimeofday({1140691193, 21209}, NULL) = 0
[pid 11295] clock_gettime(CLOCK_REALTIME, {1140691193, 21376000}) = 0
[pid 11295] futex(0x83273bc, FUTEX_WAIT, 3015, {0, 999833000}) = -1 ETIMEDOUT
(Connection timed out)
[pid 11295] futex(0x8323ac0, FUTEX_WAKE, 1) = 0
[pid 11295] gettimeofday({1140691194, 21993}, NULL) = 0
[pid 11295] clock_gettime(CLOCK_REALTIME, {1140691194, 22162000}) = 0
[pid 11295] futex(0x83273bc, FUTEX_WAIT, 3017, {0, 999831000}) = -1 ETIMEDOUT
(Connection timed out)
[pid 11295] futex(0x8323ac0, FUTEX_WAKE, 1) = 0
[pid 11295] gettimeofday({1140691195, 24540}, NULL) = 0
[pid 11295] clock_gettime(CLOCK_REALTIME, {1140691195, 24707000}) = 0
[pid 11295] futex(0x83273bc, FUTEX_WAIT, 3019, {0, 999833000}) = -1 ETIMEDOUT
(Connection timed out)
Comment 1 Alex Lancaster 2006-02-23 17:14:45 UTC
If seen this kind of thing before, typically after loading a large library ~80 Gigs.   The application never quite exits cleanly.  Will try and get a stack trace.
Comment 2 Trygve Falch 2006-02-23 18:41:59 UTC
Ah, my library is not more that 4gb, just as an additional information.

Comment 3 Jonathan Matthew 2006-06-04 03:54:54 UTC
Can you reproduce this with rhythmbox 0.9.4.1 (or cvs head)?  I haven't seen anything like this recently.  A stack trace or some sysprof data would be very helpful in tracking this down.
Comment 4 Trygve Falch 2006-06-06 14:26:02 UTC
Huhm.. how embarrasing, I'm running version 0.9.3.1 in Dapper now, and now I can't seem to be able to reproduce it anymore.

Maybe it should just be closed then?
Comment 5 André Klapper 2006-09-28 13:13:51 UTC
closing as per last comment, thanks for the feedback :-)