1846114 - On Android phones, the debugger can cause webpage lagging.

Status: RESOLVED DUPLICATE of bug 1846115

(GeckoView :: General, defect)

Description

[jian]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36 Edg/115.0.1901.183

Steps to reproduce:

To prevent web pages from being debugged, the industry typically employs a timer to enter the debugger loop.
just like：
setInterval(function(){
check();
}, 2000);
var check = function(){
function doCheck(a){
if (('' + a / a)['length'] !== 1 || a % 20 === 0){
(function() {}'constructor'());
} else {
(function() {}'constructor'());
}
doCheck(++a);
}
try {
doCheck(0);
}catch(err){}
};
check();

In Firefox browser on Android, there may be lags or slowdowns when the page is scrolling or when there are canvas drawings present.

Actual results:

I have created a test website to test for you. When you click the button in the top-left corner, the yellow ball rotation becomes laggy.
https://www.yjllq.com/fpstest.html

Expected results:

I believe that the Android version of Firefox (GeckoView) should have a master switch. When the device is connected for debugging, this master switch would be turned on, and the debugger would take effect. At other times, the debugger should be an empty implementation and not cause any lag.

Comment 1

[jian]

After testing, we found that the desktop version of Firefox also experiences lag due to the debugger.

Comment 2

[jian]

It seems that Chrome is performing smoothly despite the debugger being active.