GNOME Bugzilla – Bug 624598
[adder] crash in orc_sse_set_mxcsr()
Last modified: 2011-05-12 14:37:20 UTC
Version: 0.12.8 What were you doing when the application crashed? Rhythmbox was freshly started, a song was selected and crashed when rhythmbox started playing. When turning off the smooth transition between songs, then rhythmbox doesn't crash. Distribution: Debian squeeze/sid Gnome Release: 2.30.0 2010-04-26 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-5-amd64 #1 SMP Sun Jul 11 01:44:28 UTC 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 880795648 vsize: 880795648 resident: 94154752 share: 34689024 rss: 94154752 rss_rlim: 18446744073709551615 CPU usage: start_time: 1279356856 rtime: 652 utime: 565 stime: 87 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0x7fb5fab9d710 (LWP 6418)] [New Thread 0x7fb60171e710 (LWP 6417)] [New Thread 0x7fb60f46e710 (LWP 6416)] [New Thread 0x7fb60af91710 (LWP 6415)] [New Thread 0x7fb60b792710 (LWP 6414)] [New Thread 0x7fb60bf93710 (LWP 6410)] [New Thread 0x7fb614687710 (LWP 6377)] [New Thread 0x7fb61de80710 (LWP 6376)] [New Thread 0x7fb614e88710 (LWP 6374)] pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:211 in ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S Current language: auto The current source language is "auto; currently asm".
+ Trace 222884
Thread 2 (Thread 0x7fb5fab9d710 (LWP 6418))
Inferior 1 [process 6369] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors --------------------- ** Message: console message: https://mail-dev.nexit.nl/program/js/app.js?s=1277935203 @4930: this.set_unread_count("INBOX",0,true); this.set_unread_count("INBOX.Lists",78,false); found in search histroy, reapplying search Windowmanager waarschuwing:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5200003 (Muziekspel) Windowmanager waarschuwing:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. found in search histroy, reapplying search ** Message: console message: https://mail-dev.nexit.nl/program/js/app.js?s=1277935203 @4877: HTTP GET: ./?_task=mail&_action=check-recent&_t=1279356918473&_mbox=INBOX&_remote=1 ** Message: console message: https://mail-dev.nexit.nl/program/js/app.js?s=1277935203 @4930: this.set_unread_count("INBOX",0,true); this.set_unread_count("INBOX.Lists",79,false); 211 ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S: Bestand of map bestaat niet. --------------------------------------------------
The crash occurred inside liborc (called from the GStreamer adder element), but I'm going to reassign this to GStreamer since I don't know where liborc bugs go.
can be a dupe of bug 540336
Is this really with gst-plugins-base 0.10.29 and not 0.10.30? (In reply to comment #2) > can be a dupe of bug 540336 That seems unlikely, where do you see similarities?
(In reply to comment #3) > Is this really with gst-plugins-base 0.10.29 and not 0.10.30? No, I just screwed up when I set the version.
Below is the set of packages and versions used to trigger the crash. The ReplayGain plugin also triggers a crash. $ LANG=C dpkg -l gstr\* rhy\* | grep ^ii ii gstreamer-tools 0.10.30-1 Tools for use with GStreamer ii gstreamer0.10-alsa 0.10.30-1 GStreamer plugin for ALSA ii gstreamer0.10-doc 0.10.30-1 GStreamer core documentation and manuals ii gstreamer0.10-esd 0.10.24-1 GStreamer plugin for ESD ii gstreamer0.10-ffmpeg 0.10.10-1 FFmpeg plugin for GStreamer ii gstreamer0.10-gnonlin 0.10.15-1 non-linear editing module for GStreamer ii gstreamer0.10-gnonlin-doc 0.10.15-1 GStreamer documentation for the non-linear e ii gstreamer0.10-nice 0.0.12-1 ICE library (GStreamer plugin) ii gstreamer0.10-plugins-bad 0.10.19-2+b1 GStreamer plugins from the "bad" set ii gstreamer0.10-plugins-bad-doc 0.10.19-2 GStreamer documentation for plugins from the ii gstreamer0.10-plugins-base 0.10.30-1 GStreamer plugins from the "base" set ii gstreamer0.10-plugins-base-apps 0.10.30-1 GStreamer helper programs from the "base" se ii gstreamer0.10-plugins-base-dbg 0.10.30-1 GStreamer plugins from the "base" set ii gstreamer0.10-plugins-base-doc 0.10.30-1 GStreamer documentation for plugins from the ii gstreamer0.10-plugins-good 0.10.24-1 GStreamer plugins from the "good" set ii gstreamer0.10-plugins-good-dbg 0.10.24-1 GStreamer plugins from the "good" set ii gstreamer0.10-plugins-good-doc 0.10.24-1 GStreamer documentation for plugins from the ii gstreamer0.10-plugins-ugly 0.10.15-1 GStreamer plugins from the "ugly" set ii gstreamer0.10-plugins-ugly-dbg 0.10.15-1 GStreamer plugins from the "ugly" set (debug ii gstreamer0.10-plugins-ugly-doc 0.10.15-1 GStreamer documentation for plugins from the ii gstreamer0.10-pulseaudio 0.10.24-1 GStreamer plugin for PulseAudio ii gstreamer0.10-sdl 0.10.19-2+b1 GStreamer plugin for SDL output ii gstreamer0.10-tools 0.10.30-1 Tools for use with GStreamer ii gstreamer0.10-x 0.10.30-1 GStreamer plugins for X11 and Pango ii rhythmbox 0.12.8-2 music player and organizer for GNOME ii rhythmbox-dbg 0.12.8-2 debugging symbols for rhythmbox ii rhythmbox-plugin-cdrecorder 0.12.8-2 burning plugin for rhythmbox music player ii rhythmbox-plugin-coherence 0.12.8-2 UPnp plugin for rhythmbox music player ii rhythmbox-plugins 0.12.8-2 plugins for rhythmbox music player
*** Bug 627681 has been marked as a duplicate of this bug. ***
Could you attach the output of orc-bugreport?
*** Bug 628000 has been marked as a duplicate of this bug. ***
Hans: ping?
*** Bug 629671 has been marked as a duplicate of this bug. ***
It appears orc-bugreport isn't part any Debian package. A quick compile of orc 0.4.6 in Debian Testing gives the following result: ./orc-bugreport --verbose test.orc Orc 0.4.6 - integrated testing tool L1 cache: 65536 L2 cache: 524288 L3 cache: 0 Parsing test.orc Segmentation fault I need to check this out, but I also saw 0.4.7 is going to enter Debian Unstable this night. I will promote it tomorrow for my machine and check if this solves the current issue.
You can get orc 0.4.9 from Debian/experimental. Nothing newer than 0.4.6 will be in testing/unstable until squeeze release. But you're right, I should put orc-bugreport into the package :)
I then may have misread http://release.debian.org/migration/testing.pl?package=orc due to IA64 and MIPS, and checking p.qa.d.o you may be right :) As for 0.4.9 in experimental, I will test those packages in the next couple of days. You need any more details btw?
Created attachment 170289 [details] After updating orc from 0.4.6 to 0.4.9
These messages below got me looking at some orc code: ORC: ERROR: orccodemem.c(235): orc_code_region_allocate_codemem(): failed to create exec map ORC: ERROR: orccodemem.c(144): orc_code_region_get_free_chunk(): assertion failed: 0 And found some leads to /tmp and after doing a "mount -o remount,exec /tmp" it works without crashing. Downgrading back to 0.4.6 and allowing to execute on /tmp it also keeps working. Looking back on p.qa.d.o tho see if their is any correlation between package updates. It looks this was introduced between 0.4.5 and 0.4.6, but I haven't checked the changes between 0.4.5 and 0.4.6.
Is this still an issue with orc 0.4.11?
If it is we should probably move this to bugs.freedesktop.org
I see that 0.4.11 is available in Debian Experimental and I will run some tests the next couple of days.
Version 1:0.4.11-1 in Debian Experimental has been installed and used for a couple of days with the noexec flag on /tmp. Everything kept working and multiple formats where used like MP3, Ogg Vorbis and FLAC. It appears this bug can be closed. Hopefully Debian Squeeze is going to contain this new version as well, but that is outside control of this bug report.
Yes the noexec flag on /tmp was the problem before, since some orc version the generated code is placed in your $HOME if /tmp is mounted with noexec.
*** Bug 635260 has been marked as a duplicate of this bug. ***
*** Bug 636908 has been marked as a duplicate of this bug. ***
*** Bug 650041 has been marked as a duplicate of this bug. ***