Bug #1094012 “[Popover] compute_shadows raise a SIGABRT” : Bugs : Slingshot

Andrea Basso (voluntatefaber) on 2012-12-27

Changed in granite:
importance:	Undecided → High

Andrea Basso (voluntatefaber) on 2013-01-13

Changed in granite:
milestone:	none → luna-beta2

Revision history for this message

Sergey "Shnatsel" Davidoff (shnatsel) wrote on 2013-03-06:

#1

Is there any specific code that triggers this or the crash occurs randomly? I haven't been experiencing it and we don't seem to get many Apport reports about it, so I'm retargeting it to beta3 following other (much more obvious) Slingshot crashes being targeted to it.

Changed in granite:
milestone:	luna-beta2 → luna-beta3

Revision history for this message

Andrea Basso (voluntatefaber) wrote on 2013-03-06: Re: [Bug 1094012] Re: [Popover] compute_shadows raise a SIGABRT

#2

Download full text (4.2 KiB)

It's kind of random, but I suspect many of Slingshot crash reports are
actually caused by this, thus we do get Apport reports, it's just that
since granite's a library it shows up in the app who had the popover
running.
Il giorno 06/mar/2013 22.35, "Sergey "Shnatsel" Davidoff" <
<email address hidden>> ha scritto:

> Is there any specific code that triggers this or the crash occurs
> randomly? I haven't been experiencing it and we don't seem to get many
> Apport reports about it, so I'm retargeting it to beta3 following other
> (much more obvious) Slingshot crashes being targeted to it.
>
> ** Changed in: granite
> Milestone: luna-beta2 => luna-beta3
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1094012
>
> Title:
> [Popover] compute_shadows raise a SIGABRT
>
> Status in Granite Framework:
> New
>
> Bug description:
> When launching Slingshot, once in a while it crashed on startup with:
> *** glibc detected *** ./slingshot-launcher: malloc(): smallbin double
> linked list corrupted: 0x09590700 ***
>
> I got a backtrace:
> #0 0xb7fdd424 in __kernel_vsyscall ()
> #1 0xb74881df in raise () from /lib/i386-linux-gnu/libc.so.6
> #2 0xb748b825 in abort () from /lib/i386-linux-gnu/libc.so.6
> #3 0xb74cff1b in ?? () from /lib/i386-linux-gnu/libc.so.6
> #4 0xb74d0f0a in ?? () from /lib/i386-linux-gnu/libc.so.6
> #5 0xb74d2c34 in ?? () from /lib/i386-linux-gnu/libc.so.6
> #6 0xb74d42eb in free () from /lib/i386-linux-gnu/libc.so.6
> #7 0xb6f083f0 in pixman_image_unref () from
> /usr/lib/i386-linux-gnu/libpixman-1.so.0
> #8 0xb731218c in ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2
> #9 0xb7336633 in cairo_surface_finish () from
> /usr/lib/i386-linux-gnu/libcairo.so.2
> #10 0xb73366f8 in cairo_surface_destroy () from
> /usr/lib/i386-linux-gnu/libcairo.so.2
> #11 0xb732771a in cairo_pattern_destroy () from
> /usr/lib/i386-linux-gnu/libcairo.so.2
> #12 0xb730c03a in ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2
> #13 0xb7301e42 in cairo_set_source () from
> /usr/lib/i386-linux-gnu/libcairo.so.2
> #14 0xb7302016 in cairo_set_source_rgba () from
> /usr/lib/i386-linux-gnu/libcairo.so.2
> #15 0xb7911a32 in gdk_cairo_set_source_rgba () from
> /usr/lib/i386-linux-gnu/libgdk-3.so.0
> #16 0xb7ede147 in granite_widgets_pop_over_compute_shadow () from
> /usr/local/lib/libgranite.so.1
> #17 0xb7edc3d1 in granite_widgets_pop_over_compute_pop_position () from
> /usr/local/lib/libgranite.so.1
> #18 0xb7edceef in granite_widgets_pop_over_move_to_rect () from
> /usr/local/lib/libgranite.so.1
> #19 0x0805287e in slingshot_slingshot_view_reposition (self=0x816f018)
> at /home/andrea/slingshot-refactor/src/SlingshotView.vala:255
> #20 0x080528f0 in slingshot_slingshot_view_show_slingshot
> (self=0x816f018) at
> /home/andrea/slingshot-refactor/src/SlingshotView.vala:262
> #21 0x08050117 in slingshot_slingshot_real_activate (base=0x830e810) at
> /home/andrea/slingshot-refactor/src/Slingshot.vala:71
> #22 0xb770d243 in g_cclosure_marshal_VOID__VOIDv () from
> /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
> #23 0xb7709db7 in ?...

It's kind of random, but I suspect many of Slingshot crash reports are
actually caused by this, thus we do get Apport reports, it's just that
since granite's a library it shows up in the app who had the popover
running.
Il giorno 06/mar/2013 22.35, "Sergey "Shnatsel" Davidoff" <
Shnatsel@gmail.com> ha scritto:

> Is there any specific code that triggers this or the crash occurs
> randomly? I haven't been experiencing it and we don't seem to get many
> Apport reports about it, so I'm retargeting it to beta3 following other
> (much more obvious) Slingshot crashes being targeted to it.
>
> ** Changed in: granite
>     Milestone: luna-beta2 => luna-beta3
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1094012
>
> Title:
>   [Popover] compute_shadows raise a SIGABRT
>
> Status in Granite Framework:
>   New
>
> Bug description:
>   When launching Slingshot, once in a while it crashed on startup with:
>   *** glibc detected *** ./slingshot-launcher: malloc(): smallbin double
>   linked list corrupted: 0x09590700 ***
>
>   I got a backtrace:
>   #0  0xb7fdd424 in __kernel_vsyscall ()
>   #1  0xb74881df in raise () from /lib/i386-linux-gnu/libc.so.6
>   #2  0xb748b825 in abort () from /lib/i386-linux-gnu/libc.so.6
>   #3  0xb74cff1b in ?? () from /lib/i386-linux-gnu/libc.so.6
>   #4  0xb74d0f0a in ?? () from /lib/i386-linux-gnu/libc.so.6
>   #5  0xb74d2c34 in ?? () from /lib/i386-linux-gnu/libc.so.6
>   #6  0xb74d42eb in free () from /lib/i386-linux-gnu/libc.so.6
>   #7  0xb6f083f0 in pixman_image_unref () from
> /usr/lib/i386-linux-gnu/libpixman-1.so.0
>   #8  0xb731218c in ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2
>   #9  0xb7336633 in cairo_surface_finish () from
> /usr/lib/i386-linux-gnu/libcairo.so.2
>   #10 0xb73366f8 in cairo_surface_destroy () from
> /usr/lib/i386-linux-gnu/libcairo.so.2
>   #11 0xb732771a in cairo_pattern_destroy () from
> /usr/lib/i386-linux-gnu/libcairo.so.2
>   #12 0xb730c03a in ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2
>   #13 0xb7301e42 in cairo_set_source () from
> /usr/lib/i386-linux-gnu/libcairo.so.2
>   #14 0xb7302016 in cairo_set_source_rgba () from
> /usr/lib/i386-linux-gnu/libcairo.so.2
>   #15 0xb7911a32 in gdk_cairo_set_source_rgba () from
> /usr/lib/i386-linux-gnu/libgdk-3.so.0
>   #16 0xb7ede147 in granite_widgets_pop_over_compute_shadow () from
> /usr/local/lib/libgranite.so.1
>   #17 0xb7edc3d1 in granite_widgets_pop_over_compute_pop_position () from
> /usr/local/lib/libgranite.so.1
>   #18 0xb7edceef in granite_widgets_pop_over_move_to_rect () from
> /usr/local/lib/libgranite.so.1
>   #19 0x0805287e in slingshot_slingshot_view_reposition (self=0x816f018)
> at /home/andrea/slingshot-refactor/src/SlingshotView.vala:255
>   #20 0x080528f0 in slingshot_slingshot_view_show_slingshot
> (self=0x816f018) at
> /home/andrea/slingshot-refactor/src/SlingshotView.vala:262
>   #21 0x08050117 in slingshot_slingshot_real_activate (base=0x830e810) at
> /home/andrea/slingshot-refactor/src/Slingshot.vala:71
>   #22 0xb770d243 in g_cclosure_marshal_VOID__VOIDv () from
> /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
>   #23 0xb7709db7 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
>   #24 0xb770b727 in ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
>   #25 0xb7724a29 in g_signal_emit_valist () from
> /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
>   #26 0xb7725453 in g_signal_emit () from
> /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
>   #27 0xb77e42d9 in g_application_activate () from
> /usr/lib/i386-linux-gnu/libgio-2.0.so.0
>   #28 0xb77e4648 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
>   #29 0xb77e475d in g_application_run () from
> /usr/lib/i386-linux-gnu/libgio-2.0.so.0
>   #30 0xb7ea422f in granite_application_run () from
> /usr/local/lib/libgranite.so.1
>   #31 0x080503be in slingshot_slingshot_main (args=0xbffff304,
> args_length1=1) at /home/andrea/slingshot-refactor/src/Slingshot.vala:105
>   #32 0x0805042c in main (argc=1, argv=0xbffff304) at
> /home/andrea/slingshot-refactor/src/Slingshot.vala:88
>
>   I'm not sure since I don't know backtraces very well, but it seems
>   it's compute_shadows () fault.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/granite/+bug/1094012/+subscriptions
>

Cody Garver (codygarver) on 2013-05-14

Changed in granite:
status:	New → Confirmed

Revision history for this message

Niclas Lockner (niclasl) wrote on 2013-12-31:

#3

valgrind-luna-beta1.txt Edit (97.2 KiB, text/plain)

Does this still happen?

I ran slingshot through valgrind on Luna beta 1, on an up-to-date Luna and on Ubuntu 13.10 + daily ppa and the amount of errors has been reduced quite a lot since Luna beta 1, i.e. since the bug was opened.
With vala 0.23.1, all the invalid reads found in valgrind-13.10-daily.txt will be gone also.

Revision history for this message

Niclas Lockner (niclasl) wrote on 2013-12-31:

#4

valgrind-luna.txt Edit (66.2 KiB, text/plain)

Revision history for this message

Niclas Lockner (niclasl) wrote on 2013-12-31:

#5

valgrind-13.10-daily.txt Edit (15.0 KiB, text/plain)

Revision history for this message

Cody Garver (codygarver) wrote on 2014-03-08:

#6

This will either be Fixed or Incompleted by post-Gtk 3.12 popovers

Changed in granite:
status:	Confirmed → In Progress
assignee:	nobody → Corentin Noël (tintou)

Revision history for this message

Danielle Foré (danrabbit) wrote on 2014-05-25:

#7

Okay so we should be using gtk.popover everywhere that's not Slingshot. Slingshot should be the only one still affected. Moved the report to Slingshot.

affects:	granite → slingshot
Changed in slingshot:
milestone:	isis-beta1 → none
status:	In Progress → Confirmed
assignee:	Corentin Noël (tintou) → nobody

Slingshot

[Popover] compute_shadows raise a SIGABRT

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches