Please note: we have made some forum changes regarding user data and privacy.
More info here: Planned downtime for the forum and changes.

Much crashing

Support and discussions for the x86/x64 Linux version of Pale Moon.

Moderators: trava90, satrow

Agent Orange

Much crashing

Post by Agent Orange » 2015-04-17, 17:38

The browser crashes (segfault with no terminal output) when I:
  • Cancel a file save dialogue (~100% of the time)
  • Try to save a file (~30% of the time)
  • Try to install an Add-On (sometimes)
  • Use the mouse on a form drop-down menu (each click has about a 10% chance to crash the browser; higher odds when the form has JavaScript hooks)
Pale Moon 25.3.1 x64 on Linux Mint 17.1

SvenG

Re: Much crashing

Post by SvenG » 2015-04-17, 18:42

What flavor of Mint (MATE, Cinnamon, KDE, Xfce) are you using?

Code: Select all

if ($flavor eq "KDE") {
   Are you using the Oxygen gtk engine? 
   Try changing that if ($answer eq "yes").
} else {
   Does that also happen in a blank profile?
}

squarefractal

Re: Much crashing

Post by squarefractal » 2015-04-17, 18:47

Off-topic:
@Sven: I see you like Perl a lot. You forgot your #! line though ;)

SvenG

Re: Much crashing

Post by SvenG » 2015-04-17, 19:01

squarefractal wrote:
Off-topic:
@Sven: I see you like Perl a lot. You forgot your #! line though ;)
Off-topic:
I didn't want to confuse the OP entirely. Also I never type the shebang, that what snippets are made for.

Agent Orange

Re: Much crashing

Post by Agent Orange » 2015-04-17, 21:36

SvenG wrote:What flavor of Mint (MATE, Cinnamon, KDE, Xfce) are you using?
XFCE (processor is a Pentium 4 so I don't have much choice :crazy: )

SvenG

Re: Much crashing

Post by SvenG » 2015-04-17, 22:46

Good, what happens, when you try

Code: Select all

else {
    Does that also happen in a blank profile?
}
IIRC we have users here running Mint 17.1 Xfce, so that should not cause trouble. So I would start with the profile.

dinosaur
Fanatic
Fanatic
Posts: 127
Joined: 2014-06-03, 09:26
Location: France

Re: Much crashing

Post by dinosaur » 2015-04-18, 21:11

In about:config, try setting ui.allow_platform_file_picker to false (this way, Pale Moon will use its own file picker). This should cover issues with buggy file pickers (especially GTK+ with Oxygen)...

Agent Orange

Re: Much crashing

Post by Agent Orange » 2015-04-28, 15:09

dinosaur wrote:In about:config, try setting ui.allow_platform_file_picker to false (this way, Pale Moon will use its own file picker). This should cover issues with buggy file pickers (especially GTK+ with Oxygen)...
Hmm, trying this
Pale Moon's file picker is astonishingly awful minimalist compared to the native file picker, but if it fixes the crashes (which it seems to be doing at the moment) then this would be OK as a temporary workaround.. :crazy:

Agent Orange

Re: Much crashing

Post by Agent Orange » 2015-04-28, 15:58

Welp. Setting ui.allow_platform_file_picker to false didn't fix it.

In fact, when trying to attach this very image to this very post, the browser segfaulted twice in a row with the Pale Moon built-in file uploader, but after re-enabling the native file upload dialogue, it worked. (Or at least, it didn't crash the very first time.)
Attachments
SwagginOnEm.gif
SwagginOnEm.gif (781.2 KiB) Viewed 3183 times

squarefractal

Re: Much crashing

Post by squarefractal » 2015-04-29, 05:01

Can you please try to run Pale Moon from the terminal, try to reproduce a crash and see what happens?

Agent Orange

Re: Much crashing

Post by Agent Orange » 2015-05-07, 23:38

squarefractal wrote:Can you please try to run Pale Moon from the terminal, try to reproduce a crash and see what happens?
Nothing is output to the terminal when the browser crashes, as I have already stated. (My shell points out the segfault, but that's the extent of the error diagnosis.)

Under normal operation, I get things like this spammed in bulk to the terminal:

Code: Select all

(process:2586): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
..but then again, pretty much every GTK program does this.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 24902
Joined: 2011-08-28, 17:27
Location: 58°2'16"N 14°58'31"E
Contact:

Re: Much crashing

Post by Moonchild » 2015-05-08, 21:30

The gslice terminal error is unrelated.

If it's a gtk/oxygen issue, then this is known - Still waiting for the KDE folks to fix this bug.
Your only recourse is to switch engine to something besides oxygen-gtk. the file picker dialog really doesn't have much to do with it since it's an error in how it doesn't handle any Mozilla application well that isn't in their short list of named executable programs to handle differently...

See also: bug #985986 - https://bugzilla.mozilla.org/show_bug.cgi?id=985986#c8
and the related KDE bug: https://bugs.kde.org/show_bug.cgi?id=341181
"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne
Image

Agent Orange

Re: Much crashing

Post by Agent Orange » 2015-05-10, 22:49

Moonchild wrote:The gslice terminal error is unrelated.

If it's a gtk/oxygen issue, then this is known - Still waiting for the KDE folks to fix this bug.
Your only recourse is to switch engine to something besides oxygen-gtk. the file picker dialog really doesn't have much to do with it since it's an error in how it doesn't handle any Mozilla application well that isn't in their short list of named executable programs to handle differently...

See also: bug #985986 - https://bugzilla.mozilla.org/show_bug.cgi?id=985986#c8
and the related KDE bug: https://bugs.kde.org/show_bug.cgi?id=341181
What's this about Oxygen? Isn't that a KDE thing? I'm on XFCE. And this bug I'm experiencing does NOT occur on Firefox itself, so the fact that the bug you're thinking of is on Mozilla's bugtracker makes me strongly suspect that you are thinking of a different bug.

Just to add some more data for debugging purposes: this page http://ircalc.usps.com/ triggers the crash without fail. I never managed to get the form completely filled out without the browser crashing.

squarefractal

Re: Much crashing

Post by squarefractal » 2015-05-11, 04:14

Cannot reproduce here with the mentioned site.

Your best bet is to try to reproduce the crash while running Pale Moon as:

Code: Select all

catchsegv palemoon
...although I doubt it'll produce something useful, since the binaries are heavily optimised and stripped. :think:

Please post what you get by running this command.

Agent Orange

Re: Much crashing

Post by Agent Orange » 2015-05-13, 19:38

squarefractal wrote:Cannot reproduce here with the mentioned site.

Your best bet is to try to reproduce the crash while running Pale Moon as:

Code: Select all

catchsegv palemoon
...although I doubt it'll produce something useful, since the binaries are heavily optimised and stripped. :think:

Please post what you get by running this command.
I get no additional useful output to the terminal..

Code: Select all

% catchsegv palemoon
[…normal output…]
Segmentation fault
*** Segmentation fault
% 

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 24902
Joined: 2011-08-28, 17:27
Location: 58°2'16"N 14°58'31"E
Contact:

Re: Much crashing

Post by Moonchild » 2015-05-13, 20:10

Agent Orange wrote:What's this about Oxygen? Isn't that a KDE thing? I'm on XFCE.
XFCE is a GTK window manager, so it will very likely use oxygen-gtk as default as well
And this bug I'm experiencing does NOT occur on Firefox itself, so the fact that the bug you're thinking of is on Mozilla's bugtracker makes me strongly suspect that you are thinking of a different bug.
No, it's the exact same thing. The official Firefox binary name is in the short list of binaries that receives special treatment in the engine, which is why it does not crash. The BZ bug is there since not all mozilla products are on that list (e.g. nightly, aurora, some rebranded other alternatives like iceweasel) and suffer from the same issues. Please see what I linked to.
"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne
Image

Agent Orange

Re: Much crashing

Post by Agent Orange » 2015-05-13, 23:34

Moonchild wrote:
Agent Orange wrote:What's this about Oxygen? Isn't that a KDE thing? I'm on XFCE.
XFCE is a GTK window manager, so it will very likely use oxygen-gtk as default as well
And this bug I'm experiencing does NOT occur on Firefox itself, so the fact that the bug you're thinking of is on Mozilla's bugtracker makes me strongly suspect that you are thinking of a different bug.
No, it's the exact same thing. The official Firefox binary name is in the short list of binaries that receives special treatment in the engine, which is why it does not crash. The BZ bug is there since not all mozilla products are on that list (e.g. nightly, aurora, some rebranded other alternatives like iceweasel) and suffer from the same issues. Please see what I linked to.
I suspect the oxygen engine isn't installed:

Code: Select all

% apt show gtk{2,3}-engines-oxygen
Package: gtk2-engines-oxygen
State: not installed
Multi-Arch: same
Version: 1.4.5-0ubuntu1
Priority: optional
Section: universe/x11
Maintainer: Kubuntu Developers <kubuntu-devel@lists.ubuntu.com>
Architecture: amd64
Uncompressed Size: 1,443 k
Depends: libc6 (>= 2.14), libcairo2 (>= 1.10.0), libgcc1 (>= 1:4.1.1),
         libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.26.0),
         libpango-1.0-0 (>= 1.18.0), libpangocairo-1.0-0 (>= 1.14.0), libstdc++6
         (>= 4.6), libx11-6
PreDepends: multiarch-support
Suggests: kde-config-gtk-style
Breaks: gtk2-engines-oxygen (!= 1.4.5-0ubuntu1)
Replaces: gtk2-engines-oxygen (< 1.4.5-0ubuntu1)
Description: Oxygen widget theme for GTK+-based applications
 Oxygen-Gtk is a port of the Oxygen widget style to GTK+. 
 
 It ensures visual consistency between GTK+ and Qt-based applications running
 under KDE.
Homepage: https://projects.kde.org/projects/playground/artwork/oxygen-gtk

Package: gtk3-engines-oxygen
State: not installed
Multi-Arch: same
Version: 1.3.5-0ubuntu1
Priority: optional
Section: universe/gnome
Maintainer: Kubuntu Developers <kubuntu-devel@lists.ubuntu.com>
Architecture: amd64
Uncompressed Size: 1,376 k
Depends: libc6 (>= 2.14), libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0),
         libgcc1 (>= 1:4.1.1), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>=
         2.18.0), libpango-1.0-0 (>= 1.18.0), libpangocairo-1.0-0 (>= 1.14.0),
         libstdc++6 (>= 4.6), libx11-6
PreDepends: multiarch-support
Breaks: gtk3-engines-oxygen (!= 1.3.5-0ubuntu1)
Replaces: gtk3-engines-oxygen (< 1.3.5-0ubuntu1)
Description: Oxygen widget theme for GTK3-based applications
 Oxygen-Gtk is a port of the Oxygen widget style to GTK+. 
 
 It ensures visual consistency between GTK+ and Qt-based applications running
 under KDE.
Homepage: https://projects.kde.org/projects/playground/artwork/oxygen-gtk

% 
How can I check to see if I'm using the oxygen-gtk engine?

squarefractal

Re: Much crashing

Post by squarefractal » 2015-05-14, 10:15

TL;DR this is not an oxygen-gtk issue, unlike what Moonchild has stated this thread (also proved by OP's last post). Even without OP's clarification, this wouldn't be likely a theming engine problem as has been suspected all along. I have written an explanation that will help clarify this.

BTW, can anyone make a debug build so that OP can obtain a stack trace as suggested in my previous posts? I don't have my VMs right now, so I can't do this myself.

* Longer explanation:
  • There are various GUI libs available, e.g. GTK+, GdiPlus, Qt, wxWidgets etc.
  • Many Linux applications use one of Qt or GTK+.
  • KDE is a desktop environment consisting of Qt applications. Some other programs are written in Qt, but are not part of KDE.
  • Gnome, MATE, Xfce are DEs consisting of GTK+(2/3) applications. Some other programs are written in GTK+(2/3), but are not part of any of the DEs.
  • People and distro maintainers prefer to use apps using the same library, so that bloat can be kept to a minimum, and due to another additional complexity (stated below).
  • Different toolkits would not read from the same theme files, obviously. So in a typical KDE environment, GTK+ apps would end up being unstyled (and vice versa) and look like an outlier.
  • The same goes for GTK2 and GTK3 apps.
  • For GTK2 and GTK3, this problem is resolved by shipping themes with two different sets of files that offer similar looks to both.
  • However, for Qt and GTK*, the problem is not so easy to resolve. So, a library is loaded with GTK* apps that ensures correct styling.
  • One of these libraries is oxygen-gtk.
  • OP has Xfce, which uses GTK2 (with little bits of GTK3 mixed in). There is no reason why OP will have the oxygen-gtk theme. The only way to resolve this issue is by obtaining a stack trace.
edit: an earlier version of this post said that "Moonchild was asserting" and was phrased in a rather unfortunate manner. The post has now been clarified.
Last edited by squarefractal on 2015-05-14, 12:49, edited 2 times in total.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 24902
Joined: 2011-08-28, 17:27
Location: 58°2'16"N 14°58'31"E
Contact:

Re: Much crashing

Post by Moonchild » 2015-05-14, 11:11

TL;DR: Squarefractal is probably right
I wasn't "asserting" anything, just saying it's a very likely cause because the behavior leading up to the crash is perfectly consistent.
If the OP is obviously not having the engine installed, then it must be something else, but this was NOT clear until their most recent post, no need to slam me for it.

So, since squarefractal insists on being abrasive, I'm withdrawing from this thread (and probably from the Linux board overall for a while) - I'm sure you Linux folks can figure it all out.
"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne
Image

Agent Orange

Re: Much crashing

Post by Agent Orange » 2015-05-18, 22:34

Well, it looks like Moonchild's been scared off.. :?

Does anybody have any ideas how to debug this? I've tried Pale Moon IRC, and some tech boards online, but nobody seems to be able to help.

Another thing that triggers the crash like ~70% of the time is leaving a page which has a leave-confirmation ("Do you want to leave this page?" when the tab is closed)
Using the Enter key instead of the mouse to dismiss the message seems to have slightly lower odds of triggering the crash.

Locked