10/22/2023 0 Comments Download mozilla firefox 111.0.1If somebody who can reproduce this could capture a recording in rr, maybe that would help us get to the bottom of it. I don't immediately know how to put these pieces together. Huayra confirmed that this is still true for them. On Linux we expect the default stack limit to be 8MB. This is somehow distro dependent, but messily: for example, it affects Debian 10 but not Debian 11. So there appears to be a disagreement between our self-imposed limit, and the limit from the OS. At some point in this loop, we touch a page and segfault.īefore we do this, we've done a stack check and verified that the amount of additional stack memory we're allocating does not overflow the native stack limit we've set for ourselves. Before we copy the arguments, we touch each page of the new stack frame this is only strictly necessary on Windows, but we do it on every platform for simplicity. To do so, we have to copy the values from the interpreter stack onto the native C++ stack. At some point while interpreting this function in C++, we hit the top of the loop, increment the warm up counter, and decide to tier up to use JIT code. There is now a JS function that has nearly 20000 values on the stack (which could be arguments, local variables, intermediate results of an ongoing computation, or a mix of all three). Google recently made a change to its image search page. (Unless I'm missing something, though, nobody's reported a crash on Ubuntu yet?) Our working hypothesis in that bug was that the problem was specific to the Huayra distro, but evidence in this bug seems to indicate that it affects many Debian-based distros. They're all crashing in the same way as the crashes in bug 1839139. I've taken a look at each of the crash reports linked in these comments.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |