Much crashing

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

Moderators: trava90, satrow

User avatar
trava90
Contributing developer
Contributing developer
Posts: 1510
Joined: Mon, 20 May 2013, 18:19
Location: Earth
Contact:

Re: Much crashing

Unread postby trava90 » Tue, 19 May 2015, 08:21

I can't reproduce on my parent's Linux Mint 17.1 XFCE or my wife's 17.1 Cinnamon computers. Have you tried in safe mode and/or a new profile?

squarefractal

Re: Much crashing

Unread postby squarefractal » Tue, 19 May 2015, 08:51

Agent Orange wrote: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.

The best way to debug this would be to make a Pale Moon build with the --enable-debug flags and without --enable-optimize flags, and probably on a more recent system. Apparently, the VMs that conform to the official recommendations do not have libSegFault.so and thus won't work with catchsegv.
Off-topic:
Agent Orange wrote:Well, it looks like Moonchild's been scared off.. :?

From Moonchild himself via PM:
I apologize as well - too quick to jump on your case about it.

User avatar
trava90
Contributing developer
Contributing developer
Posts: 1510
Joined: Mon, 20 May 2013, 18:19
Location: Earth
Contact:

Re: Much crashing

Unread postby trava90 » Tue, 19 May 2015, 21:04

Agent Orange, I sent you a PM with a link to download a debug build of 25.4.1 I made for you to try.

User avatar
Agent Orange
Moon lover
Moon lover
Posts: 86
Joined: Fri, 17 Apr 2015, 17:13
Location: Linux
Contact:

Re: Much crashing

Unread postby Agent Orange » Mon, 25 May 2015, 18:16

With a debugging build:

Code: Select all

% catchsegv ./palemoon

Program ./palemoon (pid = 24014) received signal 11.
Stack:
UNKNOWN [/lib/x86_64-linux-gnu/libpthread.so.0 +0x00010340]
UNKNOWN [/usr/lib/x86_64-linux-gnu/dri/r600_dri.so +0x00168A2F]
UNKNOWN [/usr/lib/x86_64-linux-gnu/dri/r600_dri.so +0x00164A27]
UNKNOWN [/usr/lib/x86_64-linux-gnu/dri/r600_dri.so +0x0016B7FF]
UNKNOWN [/tmp/palemoon/libxul.so +0x00FC848F]
UNKNOWN [/tmp/palemoon/libxul.so +0x025DF85B]
UNKNOWN [/tmp/palemoon/libxul.so +0x025E0374]
UNKNOWN [/tmp/palemoon/libxul.so +0x025DBBC1]
UNKNOWN [/tmp/palemoon/libxul.so +0x00B6B350]
UNKNOWN [/tmp/palemoon/libxul.so +0x01354E30]
UNKNOWN [/tmp/palemoon/libxul.so +0x01354F4D]
UNKNOWN [/tmp/palemoon/libxul.so +0x013508BA]
UNKNOWN [/tmp/palemoon/libxul.so +0x01D574E9]
UNKNOWN [/tmp/palemoon/libxul.so +0x01D57D36]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x0012D815]
g_closure_invoke+0x00000138 [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x000103B8]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x00021D3D]
g_signal_emit_valist+0x00000AA9 [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x000296F9]
g_signal_emit+0x00000082 [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x00029CE2]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x0023D684]
gtk_container_propagate_expose+0x00000198 [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x000B65B8]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x000B5144]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x0012D815]
g_closure_invoke+0x00000138 [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x000103B8]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x00021AFB]
g_signal_emit_valist+0x00000AA9 [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x000296F9]
g_signal_emit+0x00000082 [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x00029CE2]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x0023D684]
gtk_main_do_event+0x000003E5 [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x0012C485]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x00040EDF]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x0003DB5A]
gdk_window_process_all_updates+0x00000118 [/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x0003E438]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x0003E499]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x0001DCE7]
g_main_context_dispatch+0x00000135 [/lib/x86_64-linux-gnu/libglib-2.0.so.0 +0x00048CE5]
UNKNOWN [/lib/x86_64-linux-gnu/libglib-2.0.so.0 +0x00049048]
g_main_context_iteration+0x0000002C [/lib/x86_64-linux-gnu/libglib-2.0.so.0 +0x000490EC]
UNKNOWN [/tmp/palemoon/libxul.so +0x01D38F8A]
UNKNOWN [/tmp/palemoon/libxul.so +0x01D7D42A]
UNKNOWN [/tmp/palemoon/libxul.so +0x01D7D546]
UNKNOWN [/tmp/palemoon/libxul.so +0x0246C204]
NS_InvokeByIndex+0x000001C4 [/tmp/palemoon/libxul.so +0x02494704]
UNKNOWN [/tmp/palemoon/libxul.so +0x019905F3]
UNKNOWN [/tmp/palemoon/libxul.so +0x0199111A]
UNKNOWN [/tmp/palemoon/libxul.so +0x01997C62]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BA7D6C]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BAE890]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BB3089]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BB6D2C]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BAEA25]
UNKNOWN [/tmp/palemoon/libxul.so +0x02D01001]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BA7D6C]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BAE890]
UNKNOWN [/tmp/palemoon/libxul.so +0x02D01A91]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BA7D6C]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BAE890]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BB3089]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BB6D2C]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BAEA25]
UNKNOWN [/tmp/palemoon/libxul.so +0x02BAEF9E]
JS_CallFunctionValue(JSContext*, JSObject*, JS::Value, unsigned int, JS::Value*, JS::Value*)+0x00000131 [/tmp/palemoon/libxul.so +0x02C85393]
UNKNOWN [/tmp/palemoon/libxul.so +0x01983FEA]
UNKNOWN [/tmp/palemoon/libxul.so +0x0197AEC1]
UNKNOWN [/tmp/palemoon/libxul.so +0x02495534]
UNKNOWN [/tmp/palemoon/libxul.so +0x0249480B]
    ~0x4657BFB0

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 22326
Joined: Sun, 28 Aug 2011, 17:27
Location: 58.5°N 15.5°E
Contact:

Re: Much crashing

Unread postby Moonchild » Mon, 25 May 2015, 19:29

A stacktrace is quite useless if you don't have symbols to relate the raw addresses in libxul.so to actual function calls :)
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne

Take note: 23 November is Wolfenoot! Eat roast meat and/or cake decorated like the full moon. #wolfenoot

squarefractal

Re: Much crashing

Unread postby squarefractal » Tue, 26 May 2015, 04:57

The symbols would generally go into the executable. Firefox always enables -g without --disable-debug. Could you post the contents of about:buildconfig of the build you're using?

Also:

Code: Select all

/usr/lib/x86_64-linux-gnu/dri/r600_dri.so

Update your drivers, maybe?

User avatar
trava90
Contributing developer
Contributing developer
Posts: 1510
Joined: Mon, 20 May 2013, 18:19
Location: Earth
Contact:

Re: Much crashing

Unread postby trava90 » Tue, 26 May 2015, 20:42

squarefractal wrote:Could you post the contents of about:buildconfig of the build you're using?

Here it is for the build I made for Agent Orange:

Code: Select all

about:buildconfig

Build Machine
centos-x64

Build platform
target
x86_64-unknown-linux-gnu

Build tools
Compiler    Version    Compiler flags
gcc    gcc version 4.7.2 20121015 (Red Hat 4.7.2-5) (GCC)    -Wall -Wpointer-arith -Wdeclaration-after-statement -Werror=return-type -Wtype-limits -Wempty-body -Wsign-compare -Wno-unused -Wcast-align -std=gnu99 -fgnu89-inline -fno-strict-aliasing -ffunction-sections -fdata-sections -pthread -pipe -DDEBUG -D_DEBUG -DTRACING -g -O1 -msse2 -mfpmath=sse -fno-omit-frame-pointer

c++    gcc version 4.7.2 20121015 (Red Hat 4.7.2-5) (GCC)    -Wall -Wpointer-arith -Woverloaded-virtual -Werror=return-type -Wtype-limits -Wempty-body -Wsign-compare -Wno-invalid-offsetof -Wcast-align -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -std=gnu++0x -pthread -pipe -DDEBUG -D_DEBUG -DTRACING -g -O1 -msse2 -mfpmath=sse -fno-omit-frame-pointer
Configure arguments

--enable-official-branding --enable-application=browser --disable-installer --disable-updater --disable-tests --disable-mochitests --enable-debug --enable-strip --enable-jemalloc '--enable-optimize=-O1 -msse2 -mfpmath=sse' --x-libraries=/usr/lib

squarefractal

Re: Much crashing

Unread postby squarefractal » Wed, 27 May 2015, 05:15

I think --disable-debug and --enable-strip may conflict, depending on what options get passed to strip. It would be preferable to leave out --enable-strip.

BTW, I thought gcc on x64 would automatically target a newer machine since all x64 processors support things like SSE(2), so -msse2 and -mfpmath=sse were redundant?

User avatar
trava90
Contributing developer
Contributing developer
Posts: 1510
Joined: Mon, 20 May 2013, 18:19
Location: Earth
Contact:

Re: Much crashing

Unread postby trava90 » Wed, 27 May 2015, 12:05

Agent Orange, I'll send you a link later today with a debug version built with squarefractal's suggestions.

Off-topic:
I'm not sure on that. I use the mozconfig as provided by Moonchild.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 22326
Joined: Sun, 28 Aug 2011, 17:27
Location: 58.5°N 15.5°E
Contact:

Re: Much crashing

Unread postby Moonchild » Thu, 28 May 2015, 16:46

For a debug build it's usually better not to strip (although the symbols aren't stripped except with --enable-strip-symbols which I don't recommend at all, it makes debugging impossible).

As for the sse2 setting; gcc probably uses mixed mode, backwards compatible to x86, which might mean it has extra dispatcher code or simply doesn't use sse2 in all places it otherwise could - that's not intended for Pale Moon.

I'm completely unfamiliar with debugging on Linux, so someone else will have to assist with getting the actual stack tract with function calls.
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne

Take note: 23 November is Wolfenoot! Eat roast meat and/or cake decorated like the full moon. #wolfenoot

User avatar
Agent Orange
Moon lover
Moon lover
Posts: 86
Joined: Fri, 17 Apr 2015, 17:13
Location: Linux
Contact:

Re: Much crashing

Unread postby Agent Orange » Wed, 10 Jun 2015, 15:54

Okay, using the latest debugging build I was provided (25.4.1 Linux x64 built by trava90 with squarefractal's advice), I got this log:

Code: Select all

Program ./palemoon/palemoon (pid = 5348) received signal 11.
Stack:
UNKNOWN [/lib/x86_64-linux-gnu/libpthread.so.0 +0x00010340]
UNKNOWN [/usr/lib/x86_64-linux-gnu/dri/r600_dri.so +0x00168A2F]
UNKNOWN [/usr/lib/x86_64-linux-gnu/dri/r600_dri.so +0x00164A27]
UNKNOWN [/usr/lib/x86_64-linux-gnu/dri/r600_dri.so +0x0016B7FF]
UNKNOWN [/tmp/palemoon/libxul.so +0x00FC848F]
UNKNOWN [/tmp/palemoon/libxul.so +0x025DF85B]
UNKNOWN [/tmp/palemoon/libxul.so +0x025E0374]
UNKNOWN [/tmp/palemoon/libxul.so +0x025DBBC1]
UNKNOWN [/tmp/palemoon/libxul.so +0x00B6B350]
UNKNOWN [/tmp/palemoon/libxul.so +0x01354E30]
UNKNOWN [/tmp/palemoon/libxul.so +0x01354F4D]
UNKNOWN [/tmp/palemoon/libxul.so +0x013508BA]
UNKNOWN [/tmp/palemoon/libxul.so +0x01D574E9]
UNKNOWN [/tmp/palemoon/libxul.so +0x01D57D36]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x0012D815]
g_closure_invoke+0x00000138 [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x000103B8]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x00021D3D]
g_signal_emit_valist+0x00000AA9 [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x000296F9]
g_signal_emit+0x00000082 [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x00029CE2]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x0023D684]
gtk_container_propagate_expose+0x00000198 [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x000B65B8]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x000B5144]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x0012D815]
g_closure_invoke+0x00000138 [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x000103B8]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x00021AFB]
g_signal_emit_valist+0x00000AA9 [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x000296F9]
g_signal_emit+0x00000082 [/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 +0x00029CE2]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x0023D684]
gtk_main_do_event+0x000003E5 [/usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 +0x0012C485]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x00040EDF]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x0003DB5A]
gdk_window_process_all_updates+0x00000118 [/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x0003E438]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x0003E499]
UNKNOWN [/usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 +0x0001DCE7]
g_main_context_dispatch+0x00000135 [/lib/x86_64-linux-gnu/libglib-2.0.so.0 +0x00048CE5]
UNKNOWN [/lib/x86_64-linux-gnu/libglib-2.0.so.0 +0x00049048]
g_main_context_iteration+0x0000002C [/lib/x86_64-linux-gnu/libglib-2.0.so.0 +0x000490EC]
UNKNOWN [/tmp/palemoon/libxul.so +0x01D38F8A]
UNKNOWN [/tmp/palemoon/libxul.so +0x01D7D42A]
UNKNOWN [/tmp/palemoon/libxul.so +0x01D7D597]
UNKNOWN [/tmp/palemoon/libxul.so +0x0246C204]
UNKNOWN [/tmp/palemoon/libxul.so +0x02402AC9]
UNKNOWN [/tmp/palemoon/libxul.so +0x01E6010B]
UNKNOWN [/tmp/palemoon/libxul.so +0x024E4106]
UNKNOWN [/tmp/palemoon/libxul.so +0x024E4117]
UNKNOWN [/tmp/palemoon/libxul.so +0x024E447C]
UNKNOWN [/tmp/palemoon/libxul.so +0x01D7BCB8]
UNKNOWN [/tmp/palemoon/libxul.so +0x01AE5BD1]
UNKNOWN [/tmp/palemoon/libxul.so +0x007CDF69]
UNKNOWN [/tmp/palemoon/libxul.so +0x007CE251]
XRE_main+0x0000013B [/tmp/palemoon/libxul.so +0x007CE4DA]
UNKNOWN [./palemoon/palemoon +0x0000444D]
UNKNOWN [./palemoon/palemoon +0x00004533]
__libc_start_main+0x000000F5 [/lib/x86_64-linux-gnu/libc.so.6 +0x00021EC5]
UNKNOWN [./palemoon/palemoon +0x000037B9]


A quick overview of some stuff:
  • The crash did NOT happen with the first debugging build I tried (which happened to have had multithread disabled)
  • libpthread.so.0 seems to be the source of the error since it's the first library listed in the catchsegv dump
  • Disabling GPU accel seemed to fix the crash
  • r600_dri.so (the library responsible for hardware acceleration on Radeon cards) is also listed very high up in the error log
Conclusion: Pale Moon seems to be having problems with GPU acceleration when done on a separate thread from the main one

What can I do to provide more information to help get this bug resolved?
    ~0x4657BFB0

User avatar
Agent Orange
Moon lover
Moon lover
Posts: 86
Joined: Fri, 17 Apr 2015, 17:13
Location: Linux
Contact:

Re: Much crashing

Unread postby Agent Orange » Wed, 10 Jun 2015, 16:12

squarefractal wrote:The symbols would generally go into the executable. Firefox always enables -g without --disable-debug. Could you post the contents of about:buildconfig of the build you're using?

Also:

Code: Select all

/usr/lib/x86_64-linux-gnu/dri/r600_dri.so

Update your drivers, maybe?

I'm running the latest versions, as far as I can tell:

Code: Select all

% apt show xserver-xorg-video-nouveau libgl1-mesa-dri
Package: xserver-xorg-video-nouveau
State: installed
Automatically installed: no
Version: 1:1.0.10-1ubuntu2
Priority: optional
Section: x11
Maintainer: Ubuntu X-SWAT <ubuntu-x@lists.ubuntu.com>
Architecture: amd64
Uncompressed Size: 308 k
Depends: libc6 (>= 2.15), libdrm-nouveau2 (>= 2.4.38), libdrm2 (>= 2.4.25),
         libudev1 (>= 183), xorg-video-abi-15, xserver-xorg-core (>=
         2:1.14.99.902)
Recommends: libgl1-mesa-dri (>= 9.0)
Conflicts: xserver-xorg-video-nouveau
Provides: xorg-driver-video
Provided by: xserver-xorg-video-nouveau-lts-utopic
Description: X.Org X server -- Nouveau display driver
 This driver for the X.Org X server (see xserver-xorg for a further description)
 provides support for NVIDIA Riva, TNT, GeForce, and Quadro cards.
 
 This package provides 2D support including EXA acceleration, Xv and RandR.  3D
 functionality is provided by the libgl1-mesa-dri package.
 
 This package is built from the FreeDesktop.org xf86-video-nouveau driver.
Homepage: http://nouveau.freedesktop.org/wiki/

Package: libgl1-mesa-dri
State: installed
Automatically installed: no
Multi-Arch: same
Version: 10.1.3-0ubuntu0.4
Priority: optional
Section: libs
Maintainer: Ubuntu X-SWAT <ubuntu-x@lists.ubuntu.com>
Architecture: amd64
Uncompressed Size: 33.2 M
Depends: libc6 (>= 2.17), libdrm-intel1 (>= 2.4.48), libdrm-nouveau2 (>=
         2.4.38), libdrm-radeon1 (>= 2.4.31), libdrm2 (>= 2.4.38), libelf1 (>=
         0.142), libexpat1 (>= 2.0.1), libgcc1 (>= 1:4.1.1), libllvm3.4,
         libstdc++6 (>= 4.6)
PreDepends: multiarch-support
Recommends: libtxc-dxtn-s2tc0 | libtxc-dxtn0
Suggests: libglide3
Conflicts: xlibmesa-dri (< 1:7.0.0), xlibmesa-dri (< 1:7.0.0)
Breaks: libgl1-mesa-dri-experimental (< 7.11.1), libgl1-mesa-dri-experimental (<
        7.11.1), libgl1-mesa-glx (< 7.10.2-4), libgl1-mesa-glx (< 7.10.2-4),
        libgl1-mesa-glx-no-multiarch, libgl1-mesa-glx-no-multiarch,
        xserver-xorg-core (< 2:1.14.3-5), xserver-xorg-core (< 2:1.14.3-5),
        xserver-xorg-core-no-multiarch, xserver-xorg-core-no-multiarch,
        libgl1-mesa-dri (!= 10.1.3-0ubuntu0.4)
Replaces: libgl1-mesa-dri-experimental (< 7.11.1), libgl1-mesa-dri-experimental
          (< 7.11.1), xlibmesa-dri (< 1:7.0.0), xlibmesa-dri (< 1:7.0.0),
          libgl1-mesa-dri (< 10.1.3-0ubuntu0.4)
Provided by: libgl1-mesa-dri-lts-utopic
Description: free implementation of the OpenGL API -- DRI modules
 This version of Mesa provides GLX and DRI capabilities: it is capable of both
 direct and indirect rendering.  For direct rendering, it can use DRI modules
 from the libgl1-mesa-dri package to accelerate drawing.
 
 This package does not include the OpenGL library itself, only the DRI modules
 for accelerating direct rendering.
 
 For a complete description of Mesa, please look at the libgl1-mesa-glx package.
 
 The tdfx DRI module needs libglide3 to enable direct rendering.
Homepage: http://mesa3d.sourceforge.net/

(tl;dr is Nouveau 1.0.10 and libgl-mesa-dri 10.1.3)
    ~0x4657BFB0

User avatar
Agent Orange
Moon lover
Moon lover
Posts: 86
Joined: Fri, 17 Apr 2015, 17:13
Location: Linux
Contact:

Re: Much crashing

Unread postby Agent Orange » Wed, 10 Jun 2015, 18:15

To anybody with this problem who finds this thread:

As a temporary solution, disabling hardware acceleration works.
    ~0x4657BFB0

User avatar
trava90
Contributing developer
Contributing developer
Posts: 1510
Joined: Mon, 20 May 2013, 18:19
Location: Earth
Contact:

Re: Much crashing

Unread postby trava90 » Thu, 11 Jun 2015, 07:34

Have you tried the drivers from nVidia rather then Nouveau?

User avatar
Agent Orange
Moon lover
Moon lover
Posts: 86
Joined: Fri, 17 Apr 2015, 17:13
Location: Linux
Contact:

Re: Much crashing

Unread postby Agent Orange » Mon, 15 Jun 2015, 02:10

trava90 wrote:Have you tried the drivers from nVidia rather then Nouveau?

My graphics card is a Radeon HD 7450, actually - I might test out the proprietary drivers at some point, but for these cards, the proprietary drivers are not generally a significant improvement (especially with regards to 2D acceleration) from the open-source ones.
    ~0x4657BFB0

User avatar
trava90
Contributing developer
Contributing developer
Posts: 1510
Joined: Mon, 20 May 2013, 18:19
Location: Earth
Contact:

Re: Much crashing

Unread postby trava90 » Wed, 17 Jun 2015, 06:12

My experiences with the open source drivers for AMD cards have not been good (although it has been several years, so I'm sure they have improved since then). Just based on my experience, my next suggestion would be to try the propriety drivers and see if that resolves the crashing.


Return to “Pale Moon for Linux”

Who is online

Users browsing this forum: No registered users and 9 guests