Note

• This issue occurs even if the PC is under high stress or not.
  This issue also occurs with WebRender off only if the PC is under high usage.
  This issue seems related to WebGL (on account of the errors that appear in the Browser console) but seeing as this issue happens immediately when WebRender is turned ON maybe WebRender is to blame.
  This issue was tested on Windows 10 x32 with GeForce GTX 1050

Affected versions

• Fx 67.0b13
  Fx 66.0.3

Affected platforms

• Windows 10 x32

Steps to reproduce

1. Enable WebRender by setting the pref gfx.webrender.all.qualified to true (you need to create it if its not available)
2. Reach https://sketchfab.com/3d-models/ygark-c6d7c184ee274a53873b4ea3a3550050
3. Rotate the model in both directions pretty fast.

Expected result

• The model rotates without any lag or issues.

Actual result

• There is a lot of lag and after a few seconds the whole model flickers.

Regression range

• Will return with a regression range as soon as possible.
  This is not a recent regression as the bug also occurs on Fx 66.0.3

Additional notes

• This issue occurs even if the PC is under high stress or not.
  This issue also occurs with WebRender off only if the PC is under high usage.
  This issue seems related to WebGL (on account of the errors that appear in the Browser console) but seeing as this issue happens immediately when WebRender is turned ON maybe WebRender is to blame.
  This issue was tested on Windows 10 x32 with GeForce GTX 1050

Jessie, since this is blocking wr-68, is it safe to assume that this will not get fixed for 67?

(In reply to Neha Kochar [:neha] from comment #2)

Jessie, since this is blocking wr-68, is it safe to assume that this will not get fixed for 67?

Correct

Bulk change of P3 carryover bugs to wontfix for 68.

Alexis, can you help see if we can reproduce this? Thank you!

The reported model has been removed from the store with no explanation. I wasn't able to reproduce the issue using other random models on my Windows 10 x64, NVIDIA Quadro M2200 system.

:dcicas, are you able to see this issue with any other models, or was this one model just weird?

Hello,

Unfortunately, due to some technical difficulties our Windows 10 x32 system will not be available until next week. What I can say for certain is that I can't reproduce this issue using a Windows 10 x64 Nvidia GeForce 1050 GTX and using a 32x build.

I will leave the NI as is, until I can fully test on a Win 10 x32 system.

Hello,

Sorry for the long delay, I re-tested this issue with Fx 68.0b10 on Windows 10 x32 with Nvidia GeForce 1050GTX with webrender enabled on https://sketchfab.com/3d-models/deviljho-monster-hunter-world-ver-16300948303a4cfb9b822e87f2b82315 and the bug could be reproduced.

You can try moving the model side to side really fast, before the model is fully loaded.

Once this happened, I cant load any other models even after creating a new profile. This is the error that I get in the browser console:

RemoteWebProgress failed to call onStatusChange: [Exception... "JavaScript component does not have a method named: "onStatusChange"'JavaScript component does not have a method named: "onStatusChange"' when calling method: [nsIWebProgressListener::onStatusChange]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "JS frame :: resource://gre/modules/RemoteWebProgress.jsm :: _callProgressListeners :: line 103" data: no] RemoteWebProgress.jsm:105
_callProgressListeners resource://gre/modules/RemoteWebProgress.jsm:105
onStatusChange resource://gre/modules/RemoteWebProgress.jsm:135

Thanks for following up!

I definitely get really nasty lag while the model is loading, but everything smooths out and normalizes once it's fully loaded. I don't see any interesting errors in the JS console. It seems about the same whether I have webrender enabled or not. I see a similar effect (though less bad) in chrome.

I'll see if we have some other hardware that behaves worse on this.

Also it might help if you can attach your about:support.

Hey jeff, just sliding this across your table in case anything here jumps out to you as interesting/strange. Otherwise we're inclined to just consider this a performance issue with low priority (since things seem to smooth out once the model is loaded).

Is this a massive model? Comment #1 looks bleak!
This looks like us barely tolerating a tough workload, but nothing particularly interesting jumps out at me.

Hello,

The issue is no longer reproducible I will mark this bug as worksforme.