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 688532 - Gnome-shell seg fault when displaying too large windows.
Gnome-shell seg fault when displaying too large windows.
Status: RESOLVED DUPLICATE of bug 722266
Product: gnome-shell
Classification: Core
Component: general
3.6.x
Other GNU Hurd
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-11-17 13:51 UTC by Martin Bodin
Modified: 2014-06-02 14:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Martin Bodin 2012-11-17 13:51:44 UTC
Hi,

It takes me a long time to understand the exact cause of the problem, but I’ve finally found it.  Gnome-shell seg fault with the following message:
“      JS LOG: IBus version is too old

** (gnome-screensaver:10635): WARNING **: ekrankurteno jam ruliĝas en ĉi tiu seanco
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 14: Having multiple values in <test> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/65-ttf-sil-andika.conf", line 32: Having multiple <family> in <alias> isn't supported and may not works as expected
      JS LOG: GNOME Shell started at Sat Nov 17 2012 14:37:54 GMT+0100 (CET)
Erreur de segmentation (nekropsio elŝutita)”.
What surprises me is that Apport did not launch itself.  I have the gnome-shell-dbg package installed but not the gnome-shell-extensions.
I would be quite please to add new informations about the bug as soon as someone explains me how to do it.  (I didn’t find any way to do it simply…)

How to reproduce it:  launch Gnome-shell normally, then open Nautilus and go to a directory with a lot of files.  Select them all, right click on them and select “Properties” (I guess it’s the English translation of “Atributoj”, but I’m not sure:  it’s the most bottom button).  Nautilus will open a window (which depends on its main window in a similar way to an alert message—I guess such windows are handled differently than the others) with a huge length (for each file you selected, it will add something like 5–6 tabs, resulting in hundreds of tabs in the pop-up window).
Gnome-shell will immediately crashes.  It will continuously crashes when launching it with “gnome-shell --replace -d ":0"” as soon as this huge window is still openned.

Note that metacity handles it correctly ☺
I guess it’s just an assumation of the developpers that no window would be that large… You should tell Nautilus that it’s not very nice of them to open such a hugely large window, but Gnome-shell should have dealt with it!

Hoping it can help,
Martin.
Comment 1 Sam Thursfield 2013-11-19 21:32:29 UTC
I just ran into this bug in Fedora 18 (gnome-shell 3.6.3.1). I had a program which simply created a GtkTreeView over some data, but somehow if there were more than about 45 rows it would crash my entire session! Mysterious ... until I realised that I had forgotten to put the GtkTreeView inside a GtkScrolledWindow.
Comment 2 Florian Müllner 2014-06-02 14:04:45 UTC
Tentatively marking this as dupe of bug 722266.

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