Closed Bug 1707016 Opened 3 years ago Closed 3 years ago

(SWGL) Process Type gpu EXCEPTION_ACCESS_VIOLATION_WRITE

Categories

(Core :: Graphics: WebRender, defect, P3)

Firefox 88
defect

Tracking

()

RESOLVED INACTIVE

People

(Reporter: kntchn, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0

Steps to reproduce:

I have had constant problems with app crashes and computer freezes since building this computer. I am using an old GPU due to silicon shortage.
It is Radeon R7 250. Have done extensive stress tests and no component has been identified. I have rolled back GPU drivers, DDU, to no avail.
I have turned off hardware acceleration and turned on software webrender.

Actual results:

https://crash-stats.mozilla.org/report/index/842af64e-23a2-4d70-a40a-9f5750210422
https://crash-stats.mozilla.org/report/index/04c4b34e-2860-46da-8206-980880210422

Expected results:

No crashes. The bugs seem to blame:
Process Type gpu
Crash Reason EXCEPTION_ACCESS_VIOLATION

Is this a problem with the GPU or system RAM?

The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Graphics: WebRender
Product: Firefox → Core

Both crashes in are in SWGL.

Severity: -- → S3
Priority: -- → P3
Summary: Process Type gpu EXCEPTION_ACCESS_VIOLATION_WRITE → (SWGL) Process Type gpu EXCEPTION_ACCESS_VIOLATION_WRITE

Both of these crashes indicate you are using FF 87, but hypothetically SW-WR should be much more stable in recently released 88. Some of these bugs you are experiencing with SW-WR might be fixed.

Flags: needinfo?(kntchn)

Going to mark this as hypothetically inactive. We haven't really made any progress here, and the suspicion is still that these were fixed in later versions.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.