- 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)
Much crashing
Moderator: trava90
Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
Much crashing
The browser crashes (segfault with no terminal output) when I:
Re: Much crashing
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?
}
Re: Much crashing
Off-topic:
@Sven: I see you like Perl a lot. You forgot your #! line though
@Sven: I see you like Perl a lot. You forgot your #! line though
Re: Much crashing
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.
I didn't want to confuse the OP entirely. Also I never type the shebang, that what snippets are made for.
Re: Much crashing
XFCE (processor is a Pentium 4 so I don't have much choice )SvenG wrote:What flavor of Mint (MATE, Cinnamon, KDE, Xfce) are you using?
Re: Much crashing
Good, what happens, when you try
IIRC we have users here running Mint 17.1 Xfce, so that should not cause trouble. So I would start with the profile.
Code: Select all
else {
Does that also happen in a blank profile?
}
Re: Much crashing
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)...
Re: Much crashing
Hmm, trying thisdinosaur 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)...
Pale Moon's file picker is astonishingly
Re: Much crashing
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.)
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 (781.2 KiB) Viewed 4052 times
Re: Much crashing
Can you please try to run Pale Moon from the terminal, try to reproduce a crash and see what happens?
Re: Much crashing
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.)squarefractal wrote:Can you please try to run Pale Moon from the terminal, try to reproduce a crash and see what happens?
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
Re: Much crashing
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 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
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Much crashing
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.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
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.
Re: Much crashing
Cannot reproduce here with the mentioned site.
Your best bet is to try to reproduce the crash while running Pale Moon as:
...although I doubt it'll produce something useful, since the binaries are heavily optimised and stripped.
Please post what you get by running this command.
Your best bet is to try to reproduce the crash while running Pale Moon as:
Code: Select all
catchsegv palemoon
Please post what you get by running this command.
Re: Much crashing
I get no additional useful output to the terminal..squarefractal wrote:Cannot reproduce here with the mentioned site.
Your best bet is to try to reproduce the crash while running Pale Moon as:...although I doubt it'll produce something useful, since the binaries are heavily optimised and stripped.Code: Select all
catchsegv palemoon
Please post what you get by running this command.
Code: Select all
% catchsegv palemoon
[…normal output…]
Segmentation fault
*** Segmentation fault
%
Re: Much crashing
XFCE is a GTK window manager, so it will very likely use oxygen-gtk as default as wellAgent Orange wrote:What's this about Oxygen? Isn't that a KDE thing? I'm on XFCE.
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.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.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Much crashing
I suspect the oxygen engine isn't installed:Moonchild wrote:XFCE is a GTK window manager, so it will very likely use oxygen-gtk as default as wellAgent Orange wrote:What's this about Oxygen? Isn't that a KDE thing? I'm on XFCE.
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.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.
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
%
Re: Much crashing
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:
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.
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:
Last edited by squarefractal on 2015-05-14, 12:49, edited 2 times in total.
Re: Much crashing
TL;DR: Squarefractal is probably right
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Much crashing
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.
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.