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 652031 - Crash in clutter_paint_volume_free at clutter-paint-volume.c line 166
Crash in clutter_paint_volume_free at clutter-paint-volume.c line 166
Status: RESOLVED DUPLICATE of bug 652036
Product: clutter
Classification: Platform
Component: ClutterStage
1.6.x
Other Linux
: Normal critical
: ---
Assigned To: clutter-maint
clutter-maint
Depends on:
Blocks:
 
 
Reported: 2011-06-07 10:27 UTC by Sachin
Modified: 2011-08-22 15:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sachin 2011-06-07 10:27:04 UTC 
There seems to be a crash in the new paint class on the call of clutter_actor_show_all where we try to show all the actors in our container.


Program received signal SIGSEGV, Segmentation fault.
0x0135b77a in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
(gdb) bt

+ Trace 227405

  • #0 ??
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #1 ??
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #2 g_slice_free1
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #3 clutter_paint_volume_free
    at ./clutter-paint-volume.c line 166
  • #4 _clutter_stage_queue_actor_redraw
    at ./clutter-stage.c line 3304
  • #5 clutter_actor_queue_redraw
    at ./clutter-actor.c line 5140
  • #6 clutter_actor_queue_relayout
    at ./clutter-actor.c line 5316
  • #7 clutter_actor_set_y
    at ./clutter-actor.c line 6741
  • #8 clutter_actor_set_property
    at ./clutter-actor.c line 2796
  • #9 g_object_set_property
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #10 clutter_actor_set_final_state
    at ./clutter-actor.c line 8972
  • #11 clutter_animatable_set_final_state
    at ./clutter-animatable.c line 206
  • #12 on_alpha_notify
    at ./clutter-animation.c line 1123
  • #13 g_cclosure_marshal_VOID__PARAM
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #18 ??
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #19 ??
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #20 g_object_notify_by_pspec
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #21 timeline_new_frame_cb
    at ./clutter-alpha.c line 159
  • #22 g_cclosure_marshal_VOID(int0_t)
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #23 g_closure_invoke
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #24 ??
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #25 g_signal_emit_valist
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #26 g_signal_emit
    from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  • #27 emit_frame_signal
    at ./clutter-timeline.c line 553
  • #28 clutter_timeline_do_frame
    at ./clutter-timeline.c line 615
  • #29 _clutter_master_clock_advance
    at ./clutter-master-clock.c line 563
  • #30 clutter_clock_dispatch
    at ./clutter-master-clock.c line 365
  • #31 g_main_context_dispatch
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #32 ??
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #33 g_main_loop_run
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #34 clutter_main
    at ./clutter-main.c line 927
  • #35 main
    at mrs_address_main.c line 453
  • #36 __libc_start_main
    from /lib/i386-linux-gnu/libc.so.6
  • #37 _start 






Comment 1


Emmanuele Bassi (:ebassi)





          2011-07-01 14:01:40 UTC
        



which version of Clutter 1.6 is this?

I cannot reproduce with any of our test cases, so a small self-contained test reproducing the issue would help immensely.






Comment 2


Fabio Durán Verdugo





          2011-08-16 02:08:38 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!






Comment 3


Emmanuele Bassi (:ebassi)





          2011-08-16 08:16:11 UTC
        



re-opening, as the bug is being followed on outside of bugzilla.






Comment 4


Emmanuele Bassi (:ebassi)





          2011-08-22 15:39:57 UTC
        



this bug is actually still a duplicated of 652036 — the stack corruption just muddled up the issue.

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