[Bug 89619] Chrome crashes in 64 bit r600 driver while running google maps - bugzilla-daemon

From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89619] Chrome crashes in 64 bit r600 driver while running google maps
Date: Wed, 18 Mar 2015 00:06:11 +0000	[thread overview]
Message-ID: <bug-89619-502@http.bugs.freedesktop.org/> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1978 bytes --]

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

            Bug ID: 89619
           Summary: Chrome crashes in 64 bit r600 driver while running
                    google maps
           Product: Mesa
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: jrpstonecarver@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Sorry folks, I am new to this and will do my best.

I first reported this bug to Google. They got all the data here:

https://code.google.com/p/chromium/issues/detail?id=467821

and told me that this is a bug in the r600 driver.

Back in December I updated from 32 bit Ubuntu 12.04 to 64 bit Ubuntu 14.04 and
have had major stability issues with Chrome ever since, particularly while
using Google Maps.

This URL

https://www.google.com/maps/place/Los+Gatos,+CA+95033/@37.1893925,-121.9894751,11z/data=!4m2!3m1!1s0x808e39d2fbec72d9:0x4b03e7246671be9b

was the first time I've managed to capture something that crashes chrome
reliably, however.

At their suggestion I tried running chrome with --disable-gpu and at least with
a simple test the problem went away.

I think these drivers are the default in Ubuntu now, but they seem to be
causing me a lot of grief.

You can pickup what Google got from the crash report Chrome sent to them from
the bug listed above.

And for the time being I will figure out how to run with --disable-gpu on all
the time to see if that avoids my issue.

Failing that I guess it's time to figure out how to go back to ATI's drivers.

If there is additional data I can provide somehow, I am happy to try. I'm no
wizard, but I will follow instructions and get whatever you need if possible.

Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3504 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel