[Linux] WebGL animations from threejs.org doesn't work properly
Categories
(Core :: Graphics: CanvasWebGL, defect, P3)
Tracking
()
People
(Reporter: mberlinger, Unassigned)
Details
(Keywords: regression)
Attachments
(1 file)
20.59 KB,
text/plain
|
Details |
Affected versions
- 68.0.2
- 69.0b15
Affected platforms
- Ubuntu 18.04x64
Steps to reproduce
- Launch Firefox
- Access the following link https://threejs.org/examples/#webgl_camera_logarithmicdepthbuffer
Expected result
- Animation is played correctly
Actual result
- Animation glitches.
Regression range
- This is not a recent regression since I was able to reproduce it on 67.0b17. I’ll come with a regression range asap, in case there is an old one.
Additional notes
- I’ve reproduced this issue on a different machine with the same Graphics NVIDIA GeForce 210 and Intel Core i5-3470 (3.2 GHz) Processor.
- My machine has AMD FX(tm)-8320 Eight-Core Processor × 8
(3.50GHz) and NVIDIA GeForce 210 Graphics - see the attached txt with about:support data from my computer
- See the screencast accessing the following link : https://drive.google.com/file/d/1TYAmV2Rfo9_AnmaAEM5icm9zKwg9Dz47/view?usp=sharing
- Issue isn’t reproducible on latest Nightly
- windows and mac platforms are not affected
- no errors is browser console
Comment 1•5 years ago
|
||
Bugbug thinks this bug is a regression, but please revert this change in case of error.
Comment 2•5 years ago
|
||
I tried the STR in comment 0 on Ubuntu 18.04x64 with 68.0.2 and 69.0b15. But I could not reproduce the problem. It seems related to driver/gpu specific problem.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 4•5 years ago
|
||
We should try to bisect the fix on Nightly if possible.
Reporter | ||
Comment 5•5 years ago
|
||
I've tried to determine the regression range but for builds older than 60, WebGL animations aren’t opened and for 60 and above, builds are affected.
The issue isn’t reproducible on nightly, so I’ve tried to determine the regression range manually using beta builds.
Updated•5 years ago
|
Reporter | ||
Comment 6•5 years ago
|
||
Upon further investigation, I think I've managed to find the fix for this issue : bug 1563859
Comment 7•5 years ago
|
||
Thanks, Maria. AFAIK, Linux WebRender is still Nightly-only, so 70 will show the issue once it rides to Beta. Setting the status to affected accordingly.
Comment 8•5 years ago
|
||
Too late for 70 but we could still take a patch for 71/72.
Comment 9•4 years ago
|
||
I can't reproduce this on RENDERER: "nouveau -- NV120", mesa/nouveau 19.2.1.0, 0x10de/0x17c8.
Possibly fixed by a mesa update?
Comment 10•4 years ago
|
||
Oh but WebRender fixes it? Very strange.
Comment 11•4 years ago
|
||
Well this should mostly take care of itself when WebRender rides out for Linux+nouveau. I tried another older (though not as old as yours!) nouveau system and that worked fine.
Updated•2 years ago
|
Description
•