rcorsi

Or should we be making a fix in `AK/StackInfo.cpp`? on line 114 maybe multiple by 2 the guard page size. Just an idea.

Just looking carefully at the links of the failed CI runs I put in this issue. All of them are on "Linux, x86_64, Sanitizer, GNU / CI". Locally I am...

I just completed running locally, loops of 100 test runs of just `test-js`. Failure results are as follows: ``` Stack Size Failures 1MB 5/100 2MB 4/100 3MB 1/100 4MB 0/100...

Increasing the system stack size (using `ulimit -s XXXXX`) will not help in this case. Ladybird's Linux Github Runner's system soft limit for stack size is at 16MB, which is...

That fatal error looks related as the SingleOwner.h:50 is one line after the backtrace above ``` ../src/335264b559-a74cacaac8.clean/include/private/base/SingleOwner.h:50: fatal error: "assertf(fOwner == self || fOwner == kIllegalThreadID): ../src/335264b559-a74cacaac8.clean/src/gpu/ganesh/Device.cpp:370 Single owner failure."...

Checked with top of master 165afd8ad14c2576e94f808808d48201d9cc7ac2 and same problem is present. Backtrace has a shorter call stack, but crashes around same area ``` * thread #1 * frame #0: 0x0000000119ca4bf4...

The two previous backtraces were off the debug build. For the release build at top of master 165afd8ad14c2576e94f808808d48201d9cc7ac2 the backtrace looks like this: ``` * thread #1 * frame #0:...

Applied fix from #6854 to see if it would help. Unfortunately, still crashes at same place in the release build. Tried debug build too and on top of master, still...

If you change your commit message to something like ``` Documentation: Improve wording in main README A few changes to make sentences sound better. ``` It should pass the lint...

I don't know your knowledge of git, so I'm a little worried I will make you do something that will mess things up. Take your time and make a backup...