This is on up to date Arch with a new Linux kernel so it's definitely not this issue,but it does happen in Firefox and not in Chrome. Not just freezing one tab, no, freezes entire Firefox, multiple open windows. They use symfony (yes, PHP i know.) and the most recent major version simply freezes Firefox when one goes to the admin interface and looses connectivity. There is this open-source ecommerce software called shopware.
On a side note, I've recently experienced a similar JS/firefox/web site bug.
So if anything I'd thank Google for exposing the bug -) So is it a "bug in Firefox" Or "bug in old Linux"? I can't say with absolute certainty without researching how exactly the stack allocation in old Linux kernel works, how is it documented etc. If someone knows more, please do explain. I haven't got time to look at the history how it was changed and why in the Linux kernel and it became "not a bug". "Accessing the stack below %sp is always a bug (.)" But, that Linux kernel code that kills a process if it accesses too far from it's stack pointer has the following comment: "it's not our code, it's Linus" here is the code. I'd rather not, but when that process starts it should be factual. I don't think assigning blame is the most important thing to do when troubleshooting. Furthermore, 20k is not that much if you take the amounts of RAM current devices have.ĭon't get me wrong. Come on now! "a peculiar interpreted code" crashes your interpreter and you blame those that (allegedly) auto generated it? I realise there is a bit of tongue in cheek in there and Firefox is an amazing product, but although it's certainly not normal for a function to declare 20k variables it is not outside the realm of the language.
0 kommentar(er)
