JShelter / webextension

#150 performance.now() is called in loop in debug mode (make debug) - only developers affected, probaly only in Chromium-based browsers
Opened by polcak. Modified

Open
Close Issue

Received by e-mail. This bug only affects developers.

Summary

maintain0.18 marked as affected, it is not clear if main is also affected.

Kiwi browser on old Chromium reported as affected. Not sure if other browsers are affected.

There is a cycle between code generated by code_builders.js (line 107) and patchWindow.js (nscl, line 145). make without debug does not produce buggy code.

This needs further investigations on what is the cause of the bug and if it also affects current browsers and JShelter main branch.

It looks like 0.20.2in Chromium is also affected. Each page visit causes and unhandled exception RangeError: Maximum call stack size exceeded between Performance.replacementF:1079:27 or 1080:59 (calling xrayWindow.performance.now() at the entry to innerF that would be a new Performance.prototype.now) and Object.apply:419:25 (return func.apply(thisArg, args)).

Suggested resolution: exclude performance.now() from this debugging option.

Metadata Update from @polcak:
- Issue tagged with: bug
Metadata
None

bug

None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.