On Monday morning we (Mozilla) detected a very large crash spike affecting Firefox users on Linux, specifically on an older version of a Debian-based distribution
On Monday morning we (Mozilla) detected a very large crash spike affecting #Firefox users on Linux, specifically on an older version of a Debian-based distribution. It turned out to be an interesting bug involving the #Linux kernel and #Google JavaScript code so let me tell you about it. A thread 🧵
On Monday morning we (Mozilla) detected a very large crash spike affecting #Firefox users on Linux, specifically on an older version of a Debian-based distribution. It turned out to be an interesting bug involving the #Linux kernel and #Google JavaScript code so let me tell you about it. A thread 🧵
The crash started apparently out-of-the-blue, hitting thousands of Argentinian users on a Debian-based distro called Huayra, and specifically on version 5 which was based on Debian 10.
Everybody seemed to crash while searching for images on Google.
Google's code was allocating 20000 variables in a single frame.
maybe update your link to point to the correct post. The link you have is a post on a kbin instance which doesn't have the full details, so i need to click again
It is interesting though that we find ourselves working around a bug we did not introduce triggered by code we do not control.
I imagine a lot of a browser's codebase looks like this. From what I understand, browsers expect webmasters to screw up their markup and make allowances for it.
Sweet! Now we can do javascript with single quotes. However, myspace strips out the word "javascript" from ANYWHERE. To get around this, some browsers will actually interpret "java\nscript" as "javascript" (that's java<NEWLINE>script).
Example: <div id="mycode" expr="alert('hah!')" style="background:url('java
script:eval(document.all.mycode.expr)')">
But on principle I agree. I can't say whether Google Images works or not on my Firefox browser, because I'm using Mojeek.