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 389421 - crash in init in gst_atomic_int_set
crash in init in gst_atomic_int_set
Status: RESOLVED DUPLICATE of bug 391278
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.x
Other All
: High critical
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 390887 390888 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-25 10:38 UTC by alexander.gouk
Modified: 2007-01-16 12:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description alexander.gouk 2006-12-25 10:38:53 UTC 
What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 60399616 vsize: 0 resident: 60399616 share: 0 rss: 10178560 rss_rlim: 0
CPU usage: start_time: 1167043130 rtime: 0 utime: 22 stime: 0 cutime:21 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/mixer_applet2'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226163440 (LWP 4677)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 96843

Thread 1 (Thread -1226163440 (LWP 4677))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 _gst_debug_category_new
    from /usr/lib/libgstreamer-0.10.so.0
  • #5 _gst_debug_init
    from /usr/lib/libgstreamer-0.10.so.0
  • #6 gst_init
    from /usr/lib/libgstreamer-0.10.so.0
  • #7 g_option_context_parse
    from /usr/lib/libglib-2.0.so.0
  • #8 gst_init_check
    from /usr/lib/libgstreamer-0.10.so.0
  • #9 gst_init
    from /usr/lib/libgstreamer-0.10.so.0
  • #10 main
  • #0 __kernel_vsyscall 






Comment 1


Jens Granseuer





          2006-12-30 10:17:48 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

This looks like a gstreamer issue, so reassigning.






Comment 2


Jens Granseuer





          2006-12-30 10:18:21 UTC
        



*** Bug 390887 has been marked as a duplicate of this bug. ***






Comment 3


Jens Granseuer





          2006-12-30 10:20:39 UTC
        



*** Bug 390888 has been marked as a duplicate of this bug. ***






Comment 4


Tim-Philipp Müller





          2006-12-30 16:07:27 UTC
        



The two duplicates have more detailed (?) stack traces:





+
Trace
    98042






    

  • 
#4
gst_atomic_int_set

    • 

  • 
#5
gst_debug_category_set_threshold

    • 

  • 
#6
gst_debug_log

    • 

  • 
#7
_gst_debug_category_new

    • 








No idea what's going on here though.







Comment 5


Tim-Philipp Müller





          2007-01-16 12:06:25 UTC
        



These traces don't really make sense, going to blame this on memory corruption due ot late g_thread_init for now (somewhat plausible since it's crashing in gst_init() and the traces are lacking decent debugging symbols).


*** This bug has been marked as a duplicate of 391278 ***