Minecraft + Oracle Java + maximized always crashes with SIGSEGV (ubuntu 14.04, java 7.0_80-b15, minecraft 1.7.10)

[Martin -]

I tried playing Minecraft (a game) but it always crashes after a few minutes (5-20 minutes) with the same kind of crash.
Minecraft worked previously on this computer, a few months ago.

Steps to reproduce:
1. Start Minecraft.
2. Press single player.
3. Create a new world or load an old world.
4. Press escape to view menu.
5. Maximize the window that Minecraft is running in.
6. Wait for 5-20 minutes until crash (always crashes).

Workaround:
Do not maximize the Minecraft window. Manual resizing works without crashing.

relevant Minecraft game output:
Failed to open BO for returned DRI2 buffer (1855x1056, dri2 back buffer, named 93).
This is likely a bug in the X Server that will lead to a crash soon.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f7cc4a9e51f, pid=4648, tid=140175230424832
#
# JRE version: Java(TM) SE Runtime Environment (7.0_80-b15) (build 1.7.0_80-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.80-b11 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [i965_dri.so+0x3a851f] __driDriverGetExtensions_i915+0xa526f
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/meb1/.minecraft/hs_err_pid4648.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

What has changed and not changed since it last worked:
Regular ubuntu updates.
Probably linux kernel update
Probably updated java.
Same version of minecraft.
Probably updated/changed graphics driver.

Speculation about possible cause:
Bug in latest oracle java.
Linux kernel bug (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478989)
Bug in x-server.
Graphics driver bug (http://www.minecraftforum.net/forums/support/unmodified-minecraft-client/2466332-arch-linux-failed-to-open-bo-for-returned-dri2).

Additional information:
lsb_release -rd
Description: Ubuntu 14.04.2 LTS
Release: 14.04

Minecraft 1.7.10

http://www.webupd8.org/2012/01/install-oracle-java-jdk-7-in-ubuntu-via.html
java -version
java version "1.7.0_80"
Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)

apt-cache policy xorg
xorg:
  Installed: 1:7.7+1ubuntu8.1
  Candidate: 1:7.7+1ubuntu8.1
  Version table:
 *** 1:7.7+1ubuntu8.1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1:7.7+1ubuntu8 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Aug 1 19:50:06 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:2300]
InstallationDate: Installed on 2014-06-11 (415 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Notebook W230SS
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=93c74f51-3b61-4655-ac70-3bb96879f01f ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W230SS
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: W230SS
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.62+git20150703.676c806d-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3~git20150727+10.6.ccef8901-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3~git20150727+10.6.ccef8901-0ubuntu0ricotz~trusty
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150729.4246c633-0ubuntu0sarvatt~trusty
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2
xserver.bootTime: Sat Aug 1 18:37:08 2015
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 intel: Failed to load module "present" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 4931
 vendor CMN
xserver.version: 2:1.15.1-0ubuntu2.7

[Martin - (mbernt-mbernt)]

Also affects minecraft 1.8.8 on the same laptop. So it's probably not a bug in minecraft.

[Martin - (mbernt-mbernt)]

Tried changing to latest nvidia open source drivers (version 355.06 from nvidia-355). It did not prevent a crash.

[Martin - (mbernt-mbernt)]

I get the same java crash bug with open OpenJDK Java 7 Runtime. So it's less likely that it's a java bug.

java version:
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.14.04.1)
OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)

relevant Minecraft game output:
Failed to open BO for returned DRI2 buffer (1855x1056, dri2 back buffer, named 79).
This is likely a bug in the X Server that will lead to a crash soon.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f05b6d7c51f, pid=14131, tid=139664637269760
#
# JRE version: OpenJDK Runtime Environment (7.0_79-b14) (build 1.7.0_79-b14)
# Java VM: OpenJDK 64-Bit Server VM (24.79-b02 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea 2.5.6
# Distribution: Ubuntu 14.04 LTS, package 7u79-2.5.6-0ubuntu1.14.04.1
# Problematic frame:
# C [i965_dri.so+0x3a851f]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/meb1/.minecraft/hs_err_pid14131.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

[Martin - (mbernt-mbernt)]

I found a way to avoid the crash bug:

Do not maximize the Minecraft window. It is still possible to manually resize the window so that it's larger than the starting window size.

[penalvch (penalvch)]

Martin, thank you for reporting this and helping make Ubuntu better. A crash in Java has nothing to do with xorg. Regarding Oracle Java, please follow the instructions as per the crash report to report to Oracle directly Regarding icedtea, your crash report is missing.

Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this report since the process outlined above will deal with this issue more efficiently. Also, please do not attach your crash report manually to this report and reopen it. Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs