Bug #1790525 “gnome-shell assert failure: double free or corrupt...” : Bugs : mutter package : Ubuntu

Revision history for this message

Gert van de Kraats (gkraats) wrote on 2018-09-03:

#1

Dependencies.txt Edit (22.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (652 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (130.3 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (768 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (106.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Registers.txt Edit (458 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (6.7 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (37.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2018-09-03:

#2

StacktraceTop:
__libc_signal_restore_set (set=0xbfcd5e9c) at ../sysdeps/unix/sysv/linux/nptl-signals.h:80
__GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
__GI_abort () at abort.c:79
__libc_message (action=do_abort, fmt=<optimized out>) at ../sysdeps/posix/libc_fatal.c:181
malloc_printerr (str=str@entry=0xb6b437e8 "double free or corruption (fasttop)") at malloc.c:5350

Revision history for this message

Apport retracing service (apport) wrote on 2018-09-03: Stacktrace.txt

#3

Stacktrace.txt Edit (17.8 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2018-09-03: StacktraceSource.txt

#4

StacktraceSource.txt Edit (7.4 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2018-09-03: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (60.1 KiB, text/plain)

Changed in gnome-shell (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Revision history for this message

Gert van de Kraats (gkraats) wrote on 2018-09-03: Re: gnome-shell assert failure: double free or corruption (fasttop)

#6

Problem disappeared as soon as manually at $HOME/.config the missing monitors.xml file with the correct dual monitor configuration is written. Initial configuration of this file using the graphical interface is not possible, because the second monitor is switching on and off, because of some looping

Daniel van Vugt (vanvugt) on 2018-09-04

summary:	- gnome-shell assert failure: double free or corruption (fasttop) + gnome-shell assert failure: double free or corruption (fasttop) in + g_free() from g_error_free() from cogl_error_free() from + cogl_texture_new_with_size() from + clutter_offscreen_effect_real_create_texture()
information type:	Private → Public

Revision history for this message

Gert van de Kraats (gkraats) wrote on 2018-09-09:

#7

Download full text (4.2 KiB)

Extra info:

1.The syslog at a crash shows next error. Probably memory management at an errormemssage is not correct. Also look at the size 2560 x 1024
Sep 08 00:18:35 Gert2 gnome-shell[2141]: CoglError set over the top of a previous CoglError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1
Sep 08 00:18:35 Gert2 org.gnome.Shell.desktop[2141]: double free or corruption (fasttop)
Sep 08 00:18:35 Gert2 org.gnome.Shell.desktop[2141]: GNOME Shell crashed with signal 6

2.It looks like the problem in an older problem. At least at Ubuntu 18.04 with display manager lightdm the same crash occurs if no monitors.xml is present and dual monitor is present.

3.It looks like the problem is caused by the different sizes of the monitors.
At startup gdm3 detects next sizes for laptop-monitor and external monitor:

Sep 9 20:22:54 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (--) intel(0): Output LVDS1 using initial mode 1280x800 on pipe 1
Sep 9 20:22:54 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (--) intel(0): Output VGA1 using initial mode 1280x1024 on pipe 0

If at logon there is no monitors.xml file for the user, gdm3 by default tries to configure the external VGA1-monitor at the right of the laptop LVDS1-monitor. This fails, probably because the vertical size 800 of LVDS1 is smaller than 1024 for VGA1. gdm3 retries, which is causing a loop until VDA1-monitor is disconnected (see next log):

Sep 9 20:23:05 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 1280x800
Sep 9 20:23:13 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 2560x1024
Sep 9 20:23:13 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): switch to mode 1280x1024@60.0 on VGA1 using pipe 0, position (1280, 0), rotation normal, reflection none

Sep 9 20:23:18 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 1280x800
Sep 9 20:23:27 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 2560x1024
Sep 9 20:23:27 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): switch to mode 1280x1024@60.0 on VGA1 using pipe 0, position (1280, 0), rotation normal, reflection none

4.If monitors.xml is present with configuration of VGA1 above LVDS1, dual monitors can be used. Also in this case it is not possible to graphically configure via the displays arrangement the configuration with above sizes and VGA1 right of LVDS1.

5. A correct monitors.xml-file does not totally solve the problem.
Frequently the start if Ubuntu hangs completely before showing the logon-screen. It is showing a character screen with next last line.

[ OK ] Started GNOME Display Manager.

Syslog gives next lines then:

Sep 9 00:40:47 Gert2 gnome-shell[1309]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1573]: reference to undefined property "MetaWindowXwayland"
Sep 9 00:40:47 Gert2 gnome-shell[1309]: Failed to allocate texture: Faile...

Extra info:

1.The syslog at a crash shows next error. Probably memory management at an errormemssage is not correct. Also look at the size 2560 x 1024 
Sep 08 00:18:35 Gert2 gnome-shell[2141]: CoglError set over the top of a previous CoglError or uninitialized memory.
                                          This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
                                          The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1
 Sep 08 00:18:35 Gert2 org.gnome.Shell.desktop[2141]: double free or corruption (fasttop)
 Sep 08 00:18:35 Gert2 org.gnome.Shell.desktop[2141]: GNOME Shell crashed with signal 6

2.It looks like the problem in an older problem. At least at Ubuntu 18.04 with display manager lightdm the same crash occurs if no monitors.xml is present and dual monitor is present.

3.It looks like the problem is caused by the different sizes of the monitors.
At startup gdm3 detects next sizes for laptop-monitor and external monitor:

Sep  9 20:22:54 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (--) intel(0): Output LVDS1 using initial mode 1280x800 on pipe 1
Sep  9 20:22:54 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (--) intel(0): Output VGA1 using initial mode 1280x1024 on pipe 0

If at logon there is no monitors.xml file for the user, gdm3 by default tries to configure the external VGA1-monitor at the right of the laptop LVDS1-monitor. This fails, probably because the vertical size 800 of LVDS1 is smaller than 1024 for VGA1. gdm3 retries, which is causing a loop until VDA1-monitor is disconnected (see next log):

Sep  9 20:23:05 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 1280x800
Sep  9 20:23:13 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 2560x1024
Sep  9 20:23:13 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): switch to mode 1280x1024@60.0 on VGA1 using pipe 0, position (1280, 0), rotation normal, reflection none

Sep  9 20:23:18 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 1280x800
Sep  9 20:23:27 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): resizing framebuffer to 2560x1024
Sep  9 20:23:27 Gert2 /usr/lib/gdm3/gdm-x-session[1915]: (II) intel(0): switch to mode 1280x1024@60.0 on VGA1 using pipe 0, position (1280, 0), rotation normal, reflection none

4.If monitors.xml is present with configuration of VGA1 above LVDS1, dual monitors can be used. Also in this case it is not possible to graphically configure via the displays arrangement the configuration with above sizes and VGA1 right of LVDS1.

5. A correct monitors.xml-file does not totally solve the problem.
Frequently the start if Ubuntu hangs completely before showing the logon-screen. It is showing a character screen with next last line.

[ OK ] Started GNOME Display Manager.

Syslog gives next lines then:

Sep  9 00:40:47 Gert2 gnome-shell[1309]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1573]: reference to undefined property "MetaWindowXwayland"
Sep  9 00:40:47 Gert2 gnome-shell[1309]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Sep  9 00:40:47 Gert2 gnome-shell[1309]: CoglError set over the top of a previous CoglError or uninitialized memory.#012This indicates a bug in someone's code. You must ensure an error is NULL before it's set.#012The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1
Sep  9 00:40:47 Gert2 org.gnome.Shell.desktop[1309]: double free or corruption (fasttop)
Sep  9 00:40:48 Gert2 org.gnome.Shell.desktop[1309]: (EE) failed to read Wayland events: Connection reset by peer
Sep  9 00:40:48 Gert2 gnome-session[1290]: gnome-session-binary[1290]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
Sep  9 00:40:48 Gert2 gnome-session-binary[1290]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
Sep  9 00:40:48 Gert2 gnome-session-binary[1290]: Unrecoverable failure in required component org.gnome.Shell.desktop

6. If at the logon-screen the arrow at upper right corner is clicked (to exit), also the system hangs with character-screen and same kind of error at syslog.

Revision history for this message

Gert van de Kraats (gkraats) wrote on 2018-09-22:

#8

Download full text (8.7 KiB)

Proposed solution:

As the stacktrace below shows the problem is caused by module cogl_texture_new_with_size at cogl/cogl/deprecated/cogl/auto-texture.c .
This module is trying to create a texture with size 2560 x 1024, which is by default is configured by gdm3 with wayland for 2 monitors.
This is not supported by graphics-card, causing error "Failed to create texture 2d due to size/format constraints".
The error is freed by cogl_texture_new_with_size, but the variable skip_error is not set to NULL by the call to cogl_error_free (because the parameter is a copy).

Then module tries to allocate a slice with max_waste -1. This also fails, causing error "Sliced texture size of 2560 x 1024 not possible with max waste set to -1".
Module cogl_set_error complains about the skip_error not being NULL with message "CoglError set...", but does not set a new value to skip_error.
Also the second error is programmed to be freed by cogl_error_free at cogl_texture_new_with_size, that in this way tries to free the same memory twice. This causes the crash "double free or corruption (fasttop)", unless by accident the same memory-address is allocated again.

To solve, the statement skip_error = NULL; should be added:
cogl_texture_new_with_size (unsigned int width,
       unsigned int height,
                            CoglTextureFlags flags,
       CoglPixelFormat internal_format)
{
  CoglTexture *tex;
  CoglError *skip_error = NULL;

_COGL_GET_CONTEXT (ctx, NULL);

  if ((_cogl_util_is_pot (width) && _cogl_util_is_pot (height)) ||
      (cogl_has_feature (ctx, COGL_FEATURE_ID_TEXTURE_NPOT_BASIC) &&
       cogl_has_feature (ctx, COGL_FEATURE_ID_TEXTURE_NPOT_MIPMAP)))
    {
      /* First try creating a fast-path non-sliced texture */
      tex = COGL_TEXTURE (cogl_texture_2d_new_with_size (ctx, width, height));

_cogl_texture_set_internal_format (tex, internal_format);

      if (!cogl_texture_allocate (tex, &skip_error))
        {
          cogl_error_free (skip_error);
          skip_error = NULL;

This solution is tested and solves the problem during startup and for right corner click.

Stacktrace with modulenames/linenumbers:
Package: gnome-shell 3.30.0-1ubuntu2
Stacktrace:
#0 0xb7ef9d41 in __kernel_vsyscall ()
#1 0xb6a4e512 in __libc_signal_restore_set (set=0xbfcb8a0c) at ../sysdeps/unix/sysv/linux/internal-signals.h:84
         set = {__val = {0, 0, 1482184750, 5789784, 2237142784, 273, 273, 3080022123, 3080956952, 16, 3080959932, 16, 3080023695, 16, 3217787612, 3066097232, 3080956952, 3080959932, 19876880, 3217787612, 3080285386, 11, 0, 3080023577, 3080285340, 3080956952, 16, 3080959932, 3080016471, 3217788168, 0, 3217787712}}
         pid = <optimized out>
         tid = <optimized out>
         ret = 0
#2 0xb6a4e512 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
         set = {__val = {0, 0, 1482184750, 5789784, 2237142784, 273, 273, 3080022123, 3080956952, 16, 3080959932, 16, 3080023695, 16, 3217787612, 3066097232, 3080956952, 3080959932, 19876880, 3217787612, 3080285386, 11, 0, 3080023577, 3080285340, 3080956952, 16, 3080959932, 3080016471, 3217788168, 0, 3217787712}}
         pid = <optimized out>
         tid = <...

Proposed solution:

As the stacktrace below shows the problem is caused by  module cogl_texture_new_with_size at cogl/cogl/deprecated/cogl/auto-texture.c .
This module is trying to create a texture with size 2560 x 1024, which is by default is configured by gdm3 with wayland for 2 monitors.
This is not supported by graphics-card, causing error "Failed to create texture 2d due to size/format constraints".
The error is freed by cogl_texture_new_with_size, but the variable skip_error is not set to NULL by the call to cogl_error_free (because the parameter is a copy).

Then module tries to allocate a slice with max_waste -1. This also fails, causing error "Sliced texture size of 2560 x 1024 not possible with max waste set to -1". 
Module cogl_set_error complains about the skip_error not being NULL with message "CoglError set...", but does not set a new value to skip_error.
Also the second error is programmed to be freed by cogl_error_free at cogl_texture_new_with_size, that in this way tries to free the same memory twice. This causes the crash "double free or corruption (fasttop)", unless by accident the same memory-address is allocated again.

To solve, the statement skip_error = NULL; should be added:
cogl_texture_new_with_size (unsigned int width,
			    unsigned int height,
                            CoglTextureFlags flags,
			    CoglPixelFormat internal_format)
{
  CoglTexture *tex;
  CoglError *skip_error = NULL;

_COGL_GET_CONTEXT (ctx, NULL);

if ((_cogl_util_is_pot (width) && _cogl_util_is_pot (height)) ||
      (cogl_has_feature (ctx, COGL_FEATURE_ID_TEXTURE_NPOT_BASIC) &&
       cogl_has_feature (ctx, COGL_FEATURE_ID_TEXTURE_NPOT_MIPMAP)))
    {
      /* First try creating a fast-path non-sliced texture */
      tex = COGL_TEXTURE (cogl_texture_2d_new_with_size (ctx, width, height));

_cogl_texture_set_internal_format (tex, internal_format);

if (!cogl_texture_allocate (tex, &skip_error))
        {
          cogl_error_free (skip_error);
          skip_error = NULL;

This solution is tested and solves the problem during startup and for right corner click.

Stacktrace with modulenames/linenumbers:
Package: gnome-shell 3.30.0-1ubuntu2
Stacktrace:
 #0  0xb7ef9d41 in __kernel_vsyscall ()
 #1  0xb6a4e512 in __libc_signal_restore_set (set=0xbfcb8a0c) at ../sysdeps/unix/sysv/linux/internal-signals.h:84
         set = {__val = {0, 0, 1482184750, 5789784, 2237142784, 273, 273, 3080022123, 3080956952, 16, 3080959932, 16, 3080023695, 16, 3217787612, 3066097232, 3080956952, 3080959932, 19876880, 3217787612, 3080285386, 11, 0, 3080023577, 3080285340, 3080956952, 16, 3080959932, 3080016471, 3217788168, 0, 3217787712}}
         pid = <optimized out>
         tid = <optimized out>
         ret = 0
 #2  0xb6a4e512 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48
         set = {__val = {0, 0, 1482184750, 5789784, 2237142784, 273, 273, 3080022123, 3080956952, 16, 3080959932, 16, 3080023695, 16, 3217787612, 3066097232, 3080956952, 3080959932, 19876880, 3217787612, 3080285386, 11, 0, 3080023577, 3080285340, 3080956952, 16, 3080959932, 3080016471, 3217788168, 0, 3217787712}}
         pid = <optimized out>
         tid = <optimized out>
         ret = 0
 #3  0xb6a382b6 in __GI_abort () at abort.c:79
         save_stage = 1
         act = {__sigaction_handler = {sa_handler = 0xb7996077 <g_vasprintf+7>, sa_sigaction = 0xb7996077 <g_vasprintf+7>}, sa_mask = {__val = {3080956952, 3060745084, 3080120357, 3217787880, 3060745084, 3217788000, 32868, 20347328, 0, 28984448, 2237142784, 3060745084, 3080120310, 3080956952, 3080956952, 3217788408, 1024, 31097824, 3080018485, 3060691022, 16, 3060756628, 0, 3, 4096, 3065078356, 2, 3066019840, 4096, 3217788168, 3064530671, 0}}, sa_flags = 4096, sa_restorer = 0x3}
         sigs = {__val = {32, 0 <repeats 31 times>}}
 #4  0xb6a9074c in __libc_message (action=do_abort, fmt=<optimized out>) at ../sysdeps/posix/libc_fatal.c:181
         ap = <optimized out>
         fd = 2
         list = <optimized out>
         nlist = <optimized out>
         cp = <optimized out>
         written = <optimized out>
 #5  0xb6a975dd in malloc_printerr (str=str@entry=0xb6ba525c "double free or corruption (fasttop)") at malloc.c:5336
 #6  0xb6a98e6f in _int_free (av=<optimized out>, p=<optimized out>, have_lock=<optimized out>) at malloc.c:4216
         idx = 6
         old = <optimized out>
         old2 = <optimized out>
         size = <optimized out>
         fb = <optimized out>
         nextchunk = <optimized out>
         nextsize = <optimized out>
         nextinuse = <optimized out>
         prevsize = <optimized out>
         bck = <optimized out>
         fwd = <optimized out>
         __PRETTY_FUNCTION__ = "_int_free"
 #7  0xb7954290 in g_free () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
 #8  0xb7938c53 in g_error_free () at /usr/lib/i386-linux-gnu/libglib-2.0.so.0
 #9  0xb66d7058 in cogl_error_free (error=0x16cba70) at cogl-error.c:45
 #10 0xb66db62c in cogl_texture_new_with_size (width=2560, height=1024, flags=COGL_TEXTURE_NO_SLICING, internal_format=COGL_PIXEL_FORMAT_RGBA_8888_PRE) at deprecated/cogl-auto-texture.c:121
         tex = 0x1da83e0
         skip_error = 0x16cba70
         ctx = <optimized out>
 #11 0xb6e9a618 in clutter_offscreen_effect_real_create_texture (effect=0x23c3b00, width=2560, height=1024) at clutter-offscreen-effect.c:141
 #12 0xb6e9ab6b in update_fbo (fbo_height=<optimized out>, fbo_width=<optimized out>, effect=0x23c3b00) at clutter-offscreen-effect.c:189
         self = 0x23c3b00
         priv = 0x23c3a30
         self = 0x23c3b00
         priv = 0x23c3a30
         box = {x1 = 3.83952416e-38, y1 = -7.05064576e-06, x2 = -7.46333353e-06, y2 = -6.81363736e-06}
         stage = <optimized out>
         projection = {xx = 3.83970801e-38, yx = 3.83946587e-38, zx = 3.83939748e-38, wx = 3.83952416e-38, xy = 3.83970801e-38, yy = 3.71409562e-38, zy = -6.8135173e-06, wy = -3.49830611e-06, xz = -1.59032059, yz = 3.3734514e-37, zz = 3.83939748e-38, wz = -6.83245798e-06, xw = 3.83970801e-38, yw = 3.83946587e-38, zw = 0, ww = -1.59032059, private_member_inv = {1.33061024e-37, 3.83970801e-38, -6.83241933e-06, -2.85067945e-05, 3.83970801e-38, 3.83946587e-38, 3.83939748e-38, -2.43004561e-05, 3.83970801e-38, 3.83946587e-38, 3.83970801e-38, -1.01604956e-35, 2.80259693e-45, -2.02588271e-05, -3.4981374e-06, -7.46333353e-06}, private_member_type = 37501696, private_member_flags = 44250112, private_member__padding3 = 37501488}
         transparent = {private_member_red = 196 '\304', private_member_green = 12 '\f', private_member_blue = 81 'Q', private_member_alpha = 1 '\001', private_member_padding0 = 22088900, private_member_padding1 = 0, private_member_padding2 = 1}
         stage_width = 2560
         stage_height = 1024
         fbo_width = 2560
         fbo_height = 1024
         width = -4.73312366e-06
         height = -7.46333353e-06
         xexpand = <optimized out>
         yexpand = <optimized out>
         texture_width = <optimized out>
         texture_height = <optimized out>
 #13 0xb6e9ab6b in clutter_offscreen_effect_pre_paint (effect=0x23c3b00) at clutter-offscreen-effect.c:267
         self = 0x23c3b00
         priv = 0x23c3a30
         box = {x1 = 3.83952416e-38, y1 = -7.05064576e-06, x2 = -7.46333353e-06, y2 = -6.81363736e-06}
         stage = <optimized out>
         projection = {xx = 3.83970801e-38, yx = 3.83946587e-38, zx = 3.83939748e-38, wx = 3.83952416e-38, xy = 3.83970801e-38, yy = 3.71409562e-38, zy = -6.8135173e-06, wy = -3.49830611e-06, xz = -1.59032059, yz = 3.3734514e-37, zz = 3.83939748e-38, wz = -6.83245798e-06, xw = 3.83970801e-38, yw = 3.83946587e-38, zw = 0, ww = -1.59032059, private_member_inv = {1.33061024e-37, 3.83970801e-38, -6.83241933e-06, -2.85067945e-05, 3.83970801e-38, 3.83946587e-38, 3.83939748e-38, -2.43004561e-05, 3.83970801e-38, 3.83946587e-38, 3.83970801e-38, -1.01604956e-35, 2.80259693e-45, -2.02588271e-05, -3.4981374e-06, -7.46333353e-06}, private_member_type = 37501696, private_member_flags = 44250112, private_member__padding3 = 37501488}
         transparent = {private_member_red = 196 '\304', private_member_green = 12 '\f', private_member_blue = 81 'Q', private_member_alpha = 1 '\001', private_member_padding0 = 22088900, private_member_padding1 = 0, private_member_padding2 = 1}
         stage_width = 2560
         stage_height = 1024
         fbo_width = 2560
         fbo_height = 1024
         width = -4.73312366e-06
         height = -7.46333353e-06
         xexpand = <optimized out>
         yexpand = <optimized out>
         texture_width = <optimized out>
         texture_height = <optimized out>
 #14 0xb6e8087b in clutter_effect_real_paint (effect=0x23c3b00, flags=CLUTTER_EFFECT_PAINT_ACTOR_DIRTY) at clutter-effect.c:211
         actor_meta = 0x23c3b00
         actor = <optimized out>
         pre_paint_succeeded = <optimized out>

Daniel van Vugt (vanvugt) on 2018-10-11

Changed in mutter (Ubuntu):
importance:	Undecided → Medium
status:	New → Triaged
assignee:	nobody → Daniel van Vugt (vanvugt)

Daniel van Vugt (vanvugt) on 2018-10-11

Changed in mutter (Ubuntu):
status:	Triaged → In Progress

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2018-10-11:

#9

Thanks for your efforts.

https://gitlab.gnome.org/GNOME/mutter/merge_requests/261

Marco Trevisan (Treviño) (3v1n0) on 2019-01-16

Changed in mutter (Ubuntu):
assignee:	Daniel van Vugt (vanvugt) → Marco Trevisan (Treviño) (3v1n0)

Marco Trevisan (Treviño) (3v1n0) on 2019-01-21

Changed in gnome-shell (Ubuntu):
status:	New → In Progress

Daniel van Vugt (vanvugt) on 2019-01-22

no longer affects:

gnome-shell (Ubuntu)

Marco Trevisan (Treviño) (3v1n0) on 2019-01-25

description:

updated

Revision history for this message

Launchpad Janitor (janitor) wrote on 2019-01-25:

#10

This bug was fixed in the package mutter - 3.30.2-5

---------------
mutter (3.30.2-5) unstable; urgency=medium

  * d/p/clutter-Avoid-rounding-compensation-when-invalidating-2D-.patch,
    d/p/clutter-Fix-offscreen-effect-painting-of-clones.patch:
    - Fix offscreen-effect painting of clones in zoom mode (LP: #1767648,
      LP: #1779615)
  * d/p/cogl-auto-texture-Avoid-a-double-free-crash.patch,
    d/p/clutter-offscreen-effect-Disable-if-no-texture.patch:
    - Fix crash in dual monitor setup and gdm activation (LP: #1790525,
      LP: #1795774)

-- Marco Trevisan (Treviño) <email address hidden> Thu, 24 Jan 2019 18:00:14 +0000

Changed in mutter (Ubuntu):
status:	In Progress → Fix Released

Iain Lane (laney) on 2019-01-25

Changed in mutter (Ubuntu Bionic):
status:	New → Incomplete
status:	Incomplete → In Progress
Changed in mutter (Ubuntu Cosmic):
status:	New → In Progress
Changed in mutter (Ubuntu Bionic):
assignee:	nobody → Marco Trevisan (Treviño) (3v1n0)
Changed in mutter (Ubuntu Cosmic):
assignee:	nobody → Marco Trevisan (Treviño) (3v1n0)

Revision history for this message

Brian Murray (brian-murray) wrote on 2019-01-31: Please test proposed package

#11

Hello Gert, or anyone else affected,

Accepted mutter into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.30.2-1~ubuntu18.10.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in mutter (Ubuntu Cosmic):
status:	In Progress → Fix Committed
tags:	added: verification-needed verification-needed-cosmic

Revision history for this message

Gert van de Kraats (gkraats) wrote on 2019-02-01:

#12

Reinstalled current libmutter.
With dual monitor horizontal aside this gives
Feb 1 22:26:58 Gert2 gnome-shell[1038]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints
Feb 1 22:26:58 Gert2 gnome-shell[1038]: CoglError set over the top of a previous CoglError or uninitialized memory.#012This indicates a bug in someone's code. You must ensure an error is NULL before it's set.#012The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1

Logon-session crashes before showing logon-screen.

Installed proposed version:

apt list libmutter-3-0
Listing... Done
libmutter-3-0/cosmic-proposed,now 3.30.2-1~ubuntu18.10.3 i386 [installed]

Problem is solved by proposed package. No new other problems detected.

Gert van de Kraats (gkraats) on 2019-02-01

tags:

added: verification-done-cosmic
removed: cosmic verification-needed-cosmic

Gert van de Kraats (gkraats) on 2019-02-01

tags:

added: cosmic

Revision history for this message

Launchpad Janitor (janitor) wrote on 2019-02-25:

#13

This bug was fixed in the package mutter - 3.30.2-1~ubuntu18.10.3

---------------
mutter (3.30.2-1~ubuntu18.10.3) cosmic; urgency=medium

  * d/p/clutter-Avoid-rounding-compensation-when-invalidating-2D-.patch,
    d/p/clutter-Fix-offscreen-effect-painting-of-clones.patch:
    - Fix offscreen-effect painting of clones in zoom mode (LP: #1767648,
      LP: #1779615)
  * d/p/cogl-auto-texture-Avoid-a-double-free-crash.patch,
    d/p/clutter-offscreen-effect-Disable-if-no-texture.patch:
    - Fix crash in dual monitor setup and gdm activation (LP: #1790525,
      LP: #1795774)

-- Marco Trevisan (Treviño) <email address hidden> Fri, 25 Jan 2019 11:09:33 +0000

Changed in mutter (Ubuntu Cosmic):
status:	Fix Committed → Fix Released

Revision history for this message

Łukasz Zemczak (sil2100) wrote on 2019-02-25: Update Released

#14

The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message

Łukasz Zemczak (sil2100) wrote on 2019-02-25: Please test proposed package

#15

Hello Gert, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in mutter (Ubuntu Bionic):
status:	In Progress → Fix Committed
tags:	added: verification-needed-bionic

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2019-03-08:

#16

It appears Gert isn't using bionic and is the only person affected.

Revision history for this message

Gert van de Kraats (gkraats) wrote on 2019-03-08:

#17

Sorry, I missed the previous request to verify at bionic.
Bionic is my basic Ubuntu.
I only use cosmic for test. At the past I installed cosmic only to verify the wayland-patch for old Intel-graphics. This worked but I got a lot of other problems with unstable starting of ubuntu, caused by wayland and plymouth.

At bionic I recently have installed the same (proposed by me) patches as at cosmic, which worked.

I will verify the official proposed fix at bionic as requested and report here.

Revision history for this message

Gert van de Kraats (gkraats) wrote on 2019-03-10:

#18

Verification succeeded. Problem solved.

tags:

added: verification-done-bionic
removed: verification-needed-bionic

Daniel van Vugt (vanvugt) on 2019-03-27

tags:

added: verification-done
removed: verification-needed

Revision history for this message

Łukasz Zemczak (sil2100) wrote on 2019-04-17:

#19

Hello Gert, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

tags:

added: verification-needed verification-needed-bionic
removed: verification-done verification-done-bionic

Revision history for this message

Gert van de Kraats (gkraats) wrote on 2019-04-19:

#20

Problem reproduced with old version:

gert@gert-laptop:~$ dpkg -s libmutter-2-0 | grep Version
Version: 3.28.3-2~ubuntu18.04.2

Apr 19 14:41:11 gert-laptop gnome-shell[991]: CoglError set over the top of a previous CoglError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1
Apr 19 14:41:11 gert-laptop org.gnome.Shell.desktop[991]: double free or corruption (fasttop)
Apr 19 14:41:11 gert-laptop org.gnome.Shell.desktop[991]: == Stack trace for context 0x1ab5838 ==
Apr 19 14:41:47 gert-laptop org.gnome.Shell.desktop[991]: (EE)
Apr 19 14:41:47 gert-laptop org.gnome.Shell.desktop[991]: Fatal server error:
Apr 19 14:41:47 gert-laptop org.gnome.Shell.desktop[991]: (EE) failed to read Wayland events: Broken pipe
Apr 19 14:41:47 gert-laptop org.gnome.Shell.desktop[991]: (EE)
Apr 19 14:41:47 gert-laptop gnome-session-binary[983]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6

After installation from proposed, the problem was solved:

root@gert-laptop:/etc/apt# dpkg -s libmutter-2-0 | grep Version
Version: 3.28.3+git20190124-0ubuntu18.04.2

Amr Ibrahim (amribrahim1987) on 2019-04-20

tags:

added: verification-done-bionic
removed: verification-needed verification-needed-bionic

Revision history for this message

Launchpad Janitor (janitor) wrote on 2019-04-25:

#21

This bug was fixed in the package mutter - 3.28.3+git20190124-0ubuntu18.04.2

---------------
mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium

  * control: Add Breaks on budgie-desktop verions broken by this upload.
    budgie-desktop needs a fix in 10.4+git20171031.10.g9f71bb8-1.2ubuntu1.2
    for compatibility with this mutter.

mutter (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium

  * New upstream git snapshot based on 3.28.3 plus commits up to 4af8d9d47
    (LP: #1811900)
    - Fix crash in dual monitor setup and gdm activation (LP: #1790525,
      LP: #1795774)
    - Make possible to launch gnome-shell in wayland using nvidia and EGLDevice
      backend (LP: #1805444)
  * debian/libmutter-2-0.symbols: Add new symbols
  * d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch,
    d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch,
    d/p/monitor-manager-Filter-out-low-screen-resolutions.patch,
    d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch,
    d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch,
    d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch,
    d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch,
    d/p/core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch,
    d/p/renderer-native-Fallback-to-non-planar-API-if-gbm_bo_get_.patch,
    d/p/clutter-x11-Implement-keycode-lookup-from-keysyms-on-virt.patch,
    d/p/clutter-Do-not-latch-modifiers-on-modifier-keys.patch:
    - Removed as applied upstream
  * d/p/clutter-Fix-offscreen-effect-painting-of-clones.patch:
    - Fix offscreen-effect painting of clones in zoom mode (LP: #1767648,
      LP: #1779615)

-- Iain Lane <email address hidden> Wed, 17 Apr 2019 11:35:51 +0100

Changed in mutter (Ubuntu Bionic):
status:	Fix Committed → Fix Released

Ubuntu
mutter package

gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture()

Bug Description

Related branches

Other bug subscribers

Bug attachments

Remote bug watches

	Status	Importance	Assigned to
mutter (Ubuntu)	Fix Released	Medium	Marco Trevisan (Treviño)
Bionic	Fix Released	Undecided	Marco Trevisan (Treviño)
Cosmic	Fix Released	Undecided	Marco Trevisan (Treviño)

Ubuntumutter package

gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture()

Bug Description

Related branches

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
mutter package