Eclipse-Community/r3dfox

r3dfox 131 problem in Windows 7

Opened this issue · 14 comments

If very often opening recieved images in messengers and press ctrl+s for save and ctrl+w for close tab , play music in WMP and use Total Commander approximately per 520-550 saves was will be flicker screen and between r3dfox and WMP , also , in task bar disappear icons see attachment as example
Screenshot_3428
In version 129 there error absent

This bug will be repeat if work 5-7 hours in browser and Total Commander and hearing music
But if I do close explorer and retry open explorer - bug will disappear , but as so this bug , I want what you fix this) I think , what this linked with methods perview on tabs in new version browser , but if disable previews , bug will remain
This in here https://github.com/Eclipse-Community/r3dfox/releases/tag/v131.0.3 , in this version i have such strange bug
I'm not use aero styles , because me this versions not want and I prefer basic style )

And so , I rollback to here https://github.com/Eclipse-Community/r3dfox/releases/tag/v129.0.2 , and I work 11 hours with browser and I can not detect problems with flickering screen or lost objects in task bar ) because I think , what need fix this problem in 131 version
Screenshot_3431
see attachment

I use Windows 7 and I haven't seen any issues like this on it with any version. Nor am I getting any other reports. This is probably something I won't be able to fix.

What need for you can fix this bug ? I use plugins in list attachment , but only 131.0.3 i have problem , maybe in 132 this bug absent , I not tested rc versions.
Screenshot_3433

I'd kinda need to be able to replicate it, then bisect to figure out the cause which takes a whole day if I'm being efficient and don't fuck it up like I usually do.

I'm migrated from Firefox 115 to R3DFox 129 and from 129.0.2 I'm trying migrate to 131.0.3.
What new in 131.0.3 if compare with 129.0.2 ? I can seeing changelog ?
I'm think , what this linked with options for previews if put the mouse pointer to the tab and recive preview on tabs , but I think , what this linked with mechanism which use for this , maybe if disable this option , all be work normally , if you not hard , try make 131.0.3 with absent this mechanism for test )
I say not disable in about:config , I say about full delete this mechanism from code browser

but I think , what this linked with mechanism which use for this , maybe if disable this option , all be work normally , if you not hard , try make 131.0.3 with absent this mechanism for test

Go to about:config and disable browser.tabs.hoverPreview.enabled

This not helped, I think what all very deep , before write here , I try disable in config
I'm trying set as in attchment and if compare sets in 129.0.2
Screenshot_3435
but for do 131.0.3 as 129.0.2 , me need set so
Screenshot_3420
maybe problem in this , I not known because asked
I'm say about this
Screenshot_3436
in 129.0.2 this not work and as I understand , this mechanism absent in 129.0.2
And this the only difference with versions 129 -> 130 and 131 , that's why I offer temporary disable this functional from in program code simply for test )
I'm agree be tester version 131 without this function )

I'm use R3DFox 129.0.2 a few days and not recive this problem about which I sayd here , I think , what need do fix 131 version and later , because if this problem appeared in 131 version , so this can be migrated problem from version to version in 131 and later )
I hope for understanding

By the way this function exists as far back as 128 so I doubt this is the issue here.

Yes , this funciton exist in 128 version , but this function for some reason not work in version 128 and 129 versions , and 129 version work very stable

It works fine for me in 128

Thank you , yes , this working in 128 ESR ) I thought earlier what this new feature which appeared in 131 version and next

K4sum1 commented

Looking a bit more carefully at this, you seem to be running the browser on a very old system. This feels like a GPU driver incompatibility that occurs due to some changes to a component in a later release.

Not sure I'd be able to fix this alone. Although it might be worth seeing if Mozilla fixes it in later releases.