[Bug 1443116] Re: Xorg crash (probably out of memory)

2015-04-12 Thread Páll Haraldsson
** Attachment added: Really?: Server terminated successfully (0). Closing log 
file
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+attachment/4373204/+files/Xorg.0.log.old

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443116

Title:
  Xorg crash(?) (probably out of memory)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1443116] Re: Xorg crash (probably out of memory)

2015-04-12 Thread Páll Haraldsson
** Attachment added: Just in case, seems this only shows correct startup after 
crash
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+attachment/4373205/+files/Xorg.0.log

** Summary changed:

- Xorg crash (probably out of memory)
+ Xorg crash(?) (probably out of memory)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443116

Title:
  Xorg crash(?) (probably out of memory)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1443116] Re: Xorg crash (probably out of memory)

2015-04-12 Thread Páll Haraldsson
** Attachment added: syslog
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+attachment/4373203/+files/syslog

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443116

Title:
  Xorg crash(?) (probably out of memory)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1443116] Re: Xorg crash(?) (probably out of memory)

2015-04-12 Thread Chris Wilson
Just to clarify, X did not crash. gnome-session crashed because of mesa
not handling the failure. X itself should be pretty robust against oom.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443116

Title:
  Xorg crash(?) (probably out of memory)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1443116] Re: Xorg crash(?) (probably out of memory)

2015-04-12 Thread Páll Haraldsson
[Not sure what (mesa) package to tag, there is a gnome-session[-bin] on likely 
(more so than mesa that is not included in logs).  Gnome-session without -bin 
ending isn't even installed (GNOME3).]

Thanks for clarifying, I think you are saying, about here is the first
real error:

Apr 12 14:30:38 Ryksugan gnome-session[1509]: intel_do_flush_locked failed: 
Cannot allocate memory
Apr 12 14:30:39 Ryksugan gnome-session[1509]: compiz (core) - Info: Loading 
plugin: core
Apr 12 14:30:39 Ryksugan gnome-session[1509]: compiz (core) - Info: Starting 
plugin: core
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: WARNING: App 
'compiz.desktop' exited with code 1
Apr 12 14:30:39 Ryksugan gnome-session[1509]: WARNING: App 'compiz.desktop' 
exited with code 1
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: WARNING: App 
'compiz.desktop' respawning too quickly
Apr 12 14:30:39 Ryksugan gnome-session[1509]: WARNING: App 'compiz.desktop' 
respawning too quickly
Apr 12 14:30:39 Ryksugan gnome-session[1509]: Unrecoverable failure in required 
component compiz.desktop
Apr 12 14:30:39 Ryksugan gnome-session[1509]: CRITICAL: We failed, but the fail 
whale is dead. Sorry
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: CRITICAL: We 
failed, but the fail whale is dead. Sorry

[Then previous (allocation) failure(s) weren't really failures, that
is, the processes handle them? At least Xorg, also compiz?]

[One thing first, if this can't be fixed for sure, even Windows had a
virtual memory low dialog box warning, years ago when I used it.
Probably easy to make for Linux, might be available as an optional
package, but should it be built in?]

Since gnome-session failed with intel_do_flush_locked failed, does
that mean this has to do with drivers (Intel graphics)? Would other GPUs
(possibly) handle better?

Good to know that X itself should be pretty robust against oom
implying oom can be survived and should be for all components such as,
mesa, ngome-session[-bin], compiz[-core], drivers (and possibly even
chrome..).

[I feel at least the Linux kernel should. Yes, it didn't really fail
here, but sometimes thrashing has been a real problem and even getting
to virtual terminal is impossible or very slow because of thrashing or
something. I feel the kernel should hold up better so I can at least go
in and kill stuff..]

If compiz[-core] is for sure not the package (with compiz.desktop) with
a problem, but possibly also a package with a problem, should I report
that or can I add it too here?


Apr 12 14:29:51 Ryksugan kernel: [15064.494054] Xorg: page allocation failure: 
order:0, mode:0xa00d4
..
Apr 12 14:30:37 Ryksugan kernel: [15110.740973] compiz: page allocation 
failure: order:0, mode:0xa00d4
..
Apr 12 14:30:37 Ryksugan kernel: [15110.743287] chromium-browse: page 
allocation failure: order:0, mode:0xa00d4
..
Apr 12 14:30:37 Ryksugan kernel: [15110.744173] chromium-browse invoked 
oom-killer: gfp_mask=0x0, order=0, oom_score_adj=200
Apr 12 14:30:37 Ryksugan kernel: [15110.744176] chromium-browse 
cpuset=session-c2.scope mems_allowed=0
..
Apr 12 14:30:37 Ryksugan kernel: [15110.744808] Out of memory: Kill process 
13574 (chromium-browse) score 364 or sacrifice child
Apr 12 14:30:37 Ryksugan kernel: [15110.744813] Killed process 13574 
(chromium-browse) total-vm:1642476kB, anon-rss:392980kB, file-rss:3536kB
Apr 12 14:30:38 Ryksugan gnome-session[1509]: intel_do_flush_locked failed: 
Cannot allocate memory
Apr 12 14:30:39 Ryksugan gnome-session[1509]: compiz (core) - Info: Loading 
plugin: core
Apr 12 14:30:39 Ryksugan gnome-session[1509]: compiz (core) - Info: Starting 
plugin: core
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: WARNING: App 
'compiz.desktop' exited with code 1
Apr 12 14:30:39 Ryksugan gnome-session[1509]: WARNING: App 'compiz.desktop' 
exited with code 1
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: WARNING: App 
'compiz.desktop' respawning too quickly
Apr 12 14:30:39 Ryksugan gnome-session[1509]: WARNING: App 'compiz.desktop' 
respawning too quickly
Apr 12 14:30:39 Ryksugan gnome-session[1509]: Unrecoverable failure in required 
component compiz.desktop
Apr 12 14:30:39 Ryksugan gnome-session[1509]: CRITICAL: We failed, but the fail 
whale is dead. Sorry
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: CRITICAL: We 
failed, but the fail whale is dead. Sorry
Apr 12 14:30:39 Ryksugan org.ayatana.bamf[1401]: ** (bamfdaemon:1435): WARNING 
**: Got an X error: BadWindow (invalid Window parameter)
Apr 12 14:30:39 Ryksugan pulseaudio[15446]: [pulseaudio] main.c: 
User-configured server at 
{f94f7f1731f6b57488f4027d53f78730}unix:/run/user/1000/pulse/native, which 
appears to be local. Probing deeper.
Apr 12 14:30:39 Ryksugan gnome-session[1509]: (nm-applet:1727): 
GLib-GObject-WARNING **: The property GtkSettings:gtk-color-palette is 
deprecated and shouldn't be used anymore. It will be removed