Testcase gets corrupted or crashes (but no crash report is generated)
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox85 | --- | unaffected |
firefox86 | --- | unaffected |
firefox87 | --- | affected |
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: regression)
Crash Data
Attachments
(2 files)
Use WR on nightly.
Open the attached testcase
On the left there will be a dropdown. Click on that dropdown and select "40"
Wait for 20-30 seconds
AR: The tab becomes black/green/corrupted. It kind of looks like a crash, but no crash report is generated.
Prior to this regression, the page would not become corrupt.
This testcase is 100% artificial, so feel free to WONTFIX or INVALID.
Updated•4 years ago
|
Reporter | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 3•4 years ago
|
||
Set release status flags based on info from the regressing bug 1688180
Comment 4•4 years ago
|
||
I did get a crash report fwiw: https://crash-stats.mozilla.org/report/index/168750de-b4c9-447e-b216-067430210215
Updated•4 years ago
|
Comment 5•4 years ago
|
||
It seems that crash reports were generated with swgl.
Updated•4 years ago
|
Comment 6•4 years ago
|
||
I saw the following message to logout. The STR made fallback to SW-WR and caused oom crash.
[GFX1-]: Attempting to allocate a texture of size 1024x8490 above the limit, trimming
[2021-02-18T07:17:08Z ERROR webrender::device::gl] Attempting to allocate a texture of size 1024x8490 above the limit, trimming
[GFX1-]: wr_renderer_render: MaxTextureSize
[GFX1-]: Fallback WR to SW-WR + D3D11
Reporter | ||
Comment 7•4 years ago
•
|
||
This looks like a dupe of bug 1501545 .
Depending on the code movement and heuristics, the testcase may start crashing, or get corrupted. I will dupe it to bug 1501545 , where there was some discussion on analysing this testcase.
Reporter | ||
Updated•4 years ago
|
Description
•