Xorg crashed with SIGABRT in OsAbort()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Random crashes that happen on high cpu load and RAM usage (not so high that a process needs to be killed, though!) when using gnome-shell. The cairo-dock session seems to be unaffected.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: xserver-xorg-core 2:1.19.3-1ubuntu6
Uname: Linux 4.13.1-
.tmp.unity_
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
BootLog:
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
CompositorUnred
CompositorUnred
Date: Thu Sep 14 08:56:38 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingI
GraphicsCard:
Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0747]
MachineType: Acer Aspire S7-391
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
CreateWellKnow
?? ()
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 11/16/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.09
dmi.board.
dmi.board.name: Storm
dmi.board.vendor: Acer
dmi.board.version: V2.09
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnInsydeCo
dmi.product.family: ChiefRiver System
dmi.product.name: Aspire S7-391
dmi.product.
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.
version.libdrm2: libdrm2 2.4.82-1
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1546541, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.