RDP crash Firefox when Screen shifts from 1440p to 2160p
Categories
(Core :: Graphics, defect, P3)
Tracking
()
People
(Reporter: thomas, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
Steps to reproduce:
PC1 started up from close (not suspend).
Firefox running on PC1 using 1440 display (2k)
RDP to PC1 from PC2 using 2160 display (4k).
PC1 running Windows 10 21H1, fully updated.
This appear to be similar to very old Bug 1219439, but this was the other way in screen size.
Actual results:
Firefox resize to the new display, but then show spinning wheel and I have to close session and reopen to continue working.
This has been an issue for several versions of Firefox and not just the most recent.
Expected results:
Firefox to resize and continue to work.
After this crash I can close and reopen the RDP session without any issues, this includes working directly on PC1 and then doing new RDP from PC2.
Comment 1•3 years ago
|
||
Thank you for submitting this report. Setting the component and waiting for the developer's opinion about it.
If this is not the correct component, please feel free to change it to a more appropriate one.
Comment 2•3 years ago
|
||
The severity field is not set for this bug.
:bhood, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 3•3 years ago
|
||
Glenn, have a gander when you get a chance, if you would please.
Comment 4•3 years ago
|
||
This is probably more of a gecko gfx or widget issue than WR. Sotaro, any ideas who would be good candidate to look at this?
Comment 5•2 years ago
|
||
When I tried, the crash did not happen, though window size became smaller.
Comment 6•2 years ago
|
||
Hi Thomas, can you check if the problem still happens?
I have not seen the issue for some time now.
Not sure exactly when it disapreared but no problems now using RDP with different resolutions.
latest tried using iPad with retita resolution, and not problems as all with any browser.
So safe to say the issue is fixed.
Thanks
Thomas
Description
•