[Mesa-dev] [Bug 38501] New: [glsl] Infinite loop when running Bioshock

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jun 20 08:36:18 PDT 2011


https://bugs.freedesktop.org/show_bug.cgi?id=38501

           Summary: [glsl] Infinite loop when running Bioshock
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Mesa core
        AssignedTo: mesa-dev at lists.freedesktop.org
        ReportedBy: sa at whiz.se


Created an attachment (id=48195)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=48195)
backtraces from bioshock

I have been trying to get the game Bioshock (running in Wine) to run with Mesa
drivers. The game will start, but when it's loading a map it just sits there,
pegging the CPU.

A backtrace seems to indicate that it's busy running the shader compiler.
Backtraces usually differs, but only up to a point, eventually they all point
back to do_common_optimization.

This might be a regression. The game was running at one point on r300g, but I
never made a note of the version of Mesa and Wine used, and so far haven't been
able to find a good starting point for a bisect. (Earlier versions of r600g
causes a GPU hang and AFAIK i965 have never worked with this game).

Setting MESA_GLSL="nopt" will cause a crash in the driver, "nopfrag" or
"nopvert" makes no difference on the bug, and using "dump" causes a crash in
hash_table_string_hash (might be separate bug?)

This is using Mesa 2fe39b46e73aea37152777fe11d489e0b1bc3f92 and Wine 1.3.22.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the mesa-dev mailing list