Crash in mesa-7.4's i915_dri.so (Java OpenGL, Runescape HD, before log on)

Bug #355742 reported by Tim Utschig
54
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Mesa
Invalid
Medium
mesa (Ubuntu)
Invalid
High
Unassigned

Bug Description

There is a new crash in i915_dri.so after updating Jaunty to the mesa-7.4 packages. I'm encountering it using the online Java-based game "Runescape" (which uses JOGL -- Java OpenGL bindings).

Steps to reproduce (no Runescape account needed):
   1. Using Ubuntu Jaunty i386 updated to the mesa-7.4 packages, and the Intel Q35 graphics chipset (other Intel chipsets likely share the same issue).
   2. Visit http://www.runescape.com/game.ws?m=1&j=1
   3. Enable HD (High-Detail) mode if not already enabled. No need to log on, the crash should happen within a few seconds.

Attached is a backtrace after recompiling the mesa-7.4 packages with extra debug info (-g3). The backtrace was taken while using Sun Java JRE 6u12, but the Java version does not seem to matter.

This particular crash does not occur on another machine with an ATI graphics card, but other crashes do, such as when you move the Firefox window, or when Firefox loses focus. It is very touchy.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: libgl1-mesa-dri 7.4-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #40-Ubuntu SMP Fri Apr 3 17:39:51 UTC 2009
SourcePackage: mesa
Uname: Linux 2.6.28-11-generic i686

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82Q35 Express DRAM Controller [8086:29b0] (rev 02)
     Subsystem: Dell Device [1028:0211]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02)
     Subsystem: Dell Device [1028:0211]

Revision history for this message
Tim Utschig (tim-tetro) wrote :

There is a new crash in i915_dri.so after updating Jaunty to the mesa-7.4 packages. I'm encountering it using the online Java-based game "Runescape" (which uses JOGL -- Java OpenGL bindings).

Steps to reproduce (no Runescape account needed):
   1. Using Ubuntu Jaunty i386 updated to the mesa-7.4 packages, and the Intel Q35 graphics chipset (other Intel chipsets likely share the same issue).
   2. Visit http://www.runescape.com/game.ws?m=1&j=1
   3. Enable HD (High-Detail) mode if not already enabled. No need to log on, the crash should happen within a few seconds.

Attached is a backtrace after recompiling the mesa-7.4 packages with extra debug info (-g3). The backtrace was taken while using Sun Java JRE 6u12, but the Java version does not seem to matter.

This particular crash does not occur on another machine with an ATI graphics card, but other crashes do, such as when you move the Firefox window, or when Firefox loses focus. It is very touchy.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: libgl1-mesa-dri 7.4-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #40-Ubuntu SMP Fri Apr 3 17:39:51 UTC 2009
SourcePackage: mesa
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
Tim Utschig (tim-tetro) wrote :
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Thanks for the backtrace! Forwarded upstream.

Changed in mesa (Ubuntu):
importance: Undecided → High
status: New → Triaged
Changed in mesa:
status: Unknown → Confirmed
Revision history for this message
In , incubusss (mdv) wrote :
Download full text (4.0 KiB)

I can confirm this on mandriva 2009.1 cooker with mesa 7.4, nexuiz crashes when vertexs are enabled :

#0 transform_points3_2d_no_rot (to_vec=0x659b7d8, m=<value optimized out>, from_vec=0x6518128) at math/m_xform_tmp.h:493
 oy = 16777215
 oz = <value optimized out>
 stride = 12
 from = (GLfloat *) 0x7fff2c503ef0
 count = 4
 m0 = 0.00249999994
 m5 = 0.00333333341
 m12 = -1
 m13 = -1
#1 0x00007f4f07bed492 in run_vertex_stage (ctx=0x647dc30, stage=<value optimized out>) at tnl/t_vb_vertex.c:144
 store = (struct vertex_stage_data *) 0x659b7b0
 tnl = (TNLcontext *) 0x6516f30
#2 0x00007f4f07be2ad4 in _tnl_run_pipeline (ctx=0x647dc30) at tnl/t_pipeline.c:158
 tnl = (TNLcontext *) 0x6516f30
 i = 0
#3 0x00007f4f07f54460 in intelRunPipeline (ctx=0x647dc30) at intel_tris.c:1079
 intel = (struct intel_context *) 0x647dc30
#4 0x00007f4f07be3659 in _tnl_draw_prims (ctx=0x647dc30, arrays=<value optimized out>, prim=0x7fff17691fd0, nr_prims=1,
    ib=0x0, min_index=12, max_index=3) at tnl/t_draw.c:402
 bo = {0x14e71d80, 0x157b8160, 0x157d8160, 0x7f4f0df56a00, 0x1f410, 0x4000, 0x7f4f0df56a00, 0x1, 0x28, 0x0, 0x64ae2b0,
  0x7f4f07b8c1d8, 0x40, 0x7f4f07bcd571, 0x120, 0x64adec8, 0x647dc30, 0x0, 0x6, 0x7f4f07bd5d97, 0x6599be0, 0x7f4f07bd5ae9,
  0x647e7b8, 0x647dc30, 0x484063, 0x7f4f07f32113, 0x647dc30, 0x647dc30, 0x0, 0x7f4f07ba222f, 0x6, 0x647dc30, 0x4}
 nr_bo = 1
 tnl = (TNLcontext *) 0x6516f30
#5 0x00007f4f07bda929 in vbo_exec_DrawArrays (mode=6, start=0, count=4) at vbo/vbo_exec_array.c:267
 ctx = (GLcontext *) 0x647dc30
 prim = {{mode = 6, indexed = 0, begin = 1, end = 1, weak = 0, pad = 0, start = 0, count = 4}}
#6 0x00007f4f07f27651 in intel_clear_tris (ctx=0x647dc30, mask=2) at intel_clear.c:225
 this_mask = 2
 color_bit = <value optimized out>
 intel = (struct intel_context *) 0x647dc30
 vertices = {{0, 0, 1}, {800, 0, 1}, {800, 600, 1}, {0, 600, 1}}
 color = {{0, 0, 0, 0}, {0, 0, 0, 0}, {0, 0, 0, 0}, {0, 0, 0, 0}}
 dst_z = <value optimized out>
 fb = <value optimized out>
 saved_fp_enable = 0 '\0'
 saved_vp_enable = 0 '\0'
 saved_shader_program = 0
 saved_active_texture = 0
#7 0x00007f4f07f279f8 in intelClear (ctx=0x647dc30, mask=770) at intel_clear.c:372
 intel = (struct intel_context *) 0x647dc30
 tri_mask = 2
 blit_mask = 768
 swrast_mask = 0
 fb = (struct gl_framebuffer *) 0x6599be0
 i = 770
#8 0x00007f4f07b36259 in _mesa_Clear (mask=17664) at main/clear.c:182
 bufferMask = 106054816
 ctx = (GLcontext *) 0x647dc30
#9 0x0000000000466bcb in strcmp () at ../sysdeps/x86_64/strcmp.S:29
No symbol table info available.
#10 0x000000000043ad0b in strcmp () at ../sysdeps/x86_64/strcmp.S:29
No symbol table info available.
#11 0x000000000043f459 in strcmp () at ../sysdeps/x86_64/strcmp.S:29
No symbol table info available.
#12 0x0000000000494645 in strcmp () at ../sysdeps/x86_64/strcmp.S:29
No symbol table info available.
#13 0x00000000004038d0 in strcmp () at ../sysdeps/x86_64/strcmp.S:29
No symbol table info available.
#14 0x00007f4f0dc17446 in __libc_start_main (main=0x403880 <strcmp+1104>, argc=1, ubp_av=0x7fff17692418,
    init=0x556070 <strcmp+1387584>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff17692408)
  ...

Read more...

Bryce Harrington (bryce)
description: updated
Revision history for this message
Richard Carter (ricket) wrote :

I'm not sure if this is going to help or not... I am experiencing the same problem, as are quite a few people, as shown by some threads in the official Runescape forums. When the applet crashes it dumps a file like "he_err_pid1234.log" in the home directory. Attached is one of those files generated just a few minutes ago from the Runescape applet, it seems to have quite a bit of debug information.

I have Ubuntu Jaunty, my video card is an Nvidia GeForce Go 7900GS, and I am using the nvidia 180.44 drivers.

Revision history for this message
Tim Utschig (tim-tetro) wrote : Re: [Bug 355742] Re: Crash in mesa-7.4's i915_dri.so (Java OpenGL, Runescape HD, before log on)

On Fri, May 08, 2009 at 10:03:22PM -0000, Ricket wrote:
> I'm not sure if this is going to help or not... I am experiencing the
> same problem,
...
> http://launchpadlibrarian.net/26482564/hs_err_pid4273.log

I think what you've encountered is a different bug. Your crash
is in libjvm.so, not a mesa library.

--
   - Tim Utschig <email address hidden>

Revision history for this message
Marshian (wereldoverheersing) wrote :

Yes, Ricket is experiencing a different bug. The one this bug report is about doesn't generate hs_err files.

I can however confirm the bug.
Ubuntu 9.04 (Jaunty)
Nvidia GeForce 8400M GS

Revision history for this message
Justin Martin (frozenfire89) wrote :

I've experienced a similar bug with Runescape in Intrepid as well.

When switching to HD mode, FireFox would crash.

In Jaunty, FireFox doesn't now crash, but rather flashes the game in HD, then goes grey. If I am quick enough, it is possible to switch back to Standard mode, recovering from the issue.

Revision history for this message
Richard Carter (ricket) wrote :

I believe my problem may have lied in mixing sun java and openjdk; I have since discovered update-java-alternatives and I now experience the same symptoms as in this bug report, with no hs_err_pid*.log file being generated any more.

I have tried increasing Java memory and using the -client switch, neither of which worked.

Is there any progress being made towards fixing this bug? Is someone out there trying to figure it out? It'd be great to have some sort of progress reports...

Thanks,
Ricket

Revision history for this message
Wayne Allen (nintendogamer01) wrote :

I'd like to update that as of a couple of weeks ago RuneScape now refuses to enter HD mode on Jaunty, presumably to prevent the client from crashing because of this bug. Also, yesterday a Jagex employee posted this on the RuneScape forums:

Mod Noldor
Jagex Mod

15-Jun-2009 17:17:38
Hi All,

We seem to have come across an issue where RuneScape is not running in HD mode on Ubuntu version 9.04. Although I can not say when this will be fixed please be aware that we are looking into the issue and will try and resolve it as soon as possible.

Sorry for any inconvenience and I will keep you updated when we make any progress.

Mod Noldor
Core Technologies QA

I mentioned this bug report on the same thread, so perhaps the Jagex team will pick this up and get it fixed.

Revision history for this message
In , Eric Anholt (eric-anholt) wrote :

When I click "HD" in runescape login, the window goes white and nothing happens.

In nexuiz, "vertex and some triangles" mode is enabled (assuming that's what was meant?), and it works except for opponents not being visible when I choose "instant action", but I don't see the bug reported here.

So, can you verify that it still exists on Mesa master, and if so, provide some more detail on how to reproduce the problem?

Revision history for this message
Marshian (wereldoverheersing) wrote :

High detail appears to be working on Ubuntu 9.04, unless anyone can confirm this isn't true I think this bug report can be closed.
Apparently the bug was on the side of RuneScape and has been fixed by Jagex.

Revision history for this message
In , Tim Utschig (tim-tetro) wrote :

Apparently this bug was fixed in Runescape by Jagex (see Launchpad # 355742). Unclear whether or not this was ever a bug in mesa.

Revision history for this message
Tim Utschig (tim-tetro) wrote :

Confirmed fixed on karmic. Checked *.so files distributed by Jagex, one differed since I last logged in several days ago.

   $ diff -r jogl-*
   Binary files jogl-20090708/libjaggl.so and jogl-b4-20090708/libjaggl.so differ
   $ ls -l jogl-20090708/libjaggl.so jogl-b4-20090708/libjaggl.so
   -rw-r--r-- 1 tim tim 73236 2009-07-09 08:20 jogl-20090708/libjaggl.so
   -rw-r--r-- 1 tim tim 50952 2009-06-27 06:20 jogl-b4-20090708/libjaggl.so

It is unclear whether or not the bug was in Jagex's code, or whether Jagex simply worked around the mesa bug.

Since I am now unable to reproduce this bug, I'll close it. If I can figure out how...

Changed in mesa (Ubuntu):
status: Triaged → Invalid
Changed in mesa:
status: Confirmed → Invalid
Revision history for this message
Richard Carter (ricket) wrote :

Confirmed, works for me too! Yay, I can go back to using Ubuntu now! :)

Changed in mesa:
importance: Unknown → Medium
Changed in mesa:
importance: Medium → Unknown
Changed in mesa:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.