Open Bug 1400811 Opened 2 years ago Updated Last year
Increase the size of the run-time stack for the thread that runs the frame constructor on Fennec/Aarch64
Currently, Fennec on Aarch64 has enough stack space for the frame constructor to deal with 380 nested display: blocks. This is insufficient for getting compatibility with Chrome's handling of deeply-nested HTML, which requires the frame constructor to be able to deal with a depth of 513 + plus some. (Fennec on 32-bit ARM can now do 597, so my current plan is to make "513 plus some" equal 590 on Android even though I'm aiming for 1026, i.e. 513*2, on desktop Linux.) Ideally, Fennec would set the max stack size to desktopish numbers. (8 MB on desktop Linux for the main thread.)
Where might I find the code that creates the Gecko main thread on Android?
We create it in Java here, and the main loop entry point is the GeckoLoader.nativeRun() call which is implemented here  https://dxr.mozilla.org/mozilla-central/rev/97efdde466f18cf580fda9673cf4c38ee21fc7b7/mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoThread.java  https://dxr.mozilla.org/mozilla-central/rev/97efdde466f18cf580fda9673cf4c38ee21fc7b7/mozglue/android/APKOpen.cpp#411
Priority: -- → P3
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Needinfo :susheel if you think this bug should be re-triaged.
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.