I don't know if this bug is related to https://bugzilla.mozilla.org/show_bug.cgi?id=1890537 (I've the feeling it could be), but if it's the case, we've some profiles in this bug which are showing that the `AndroidIU (JVM)` thread is doing a lot of things when almost nothing is done on the Gecko side (or pdf.js). I wonder if the stacks ending with `org.mozilla.fenix.FenixApplication.onTrimMemory` could indicate that the OS doesn't have enough memory or something like that and we're trying in Gecko to release some memory but it takes too much time, and then the OS spends too much time to empty then event queue containing the MotionEvent.
Bug 1896513 Comment 21 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I don't know if this bug is related to https://bugzilla.mozilla.org/show_bug.cgi?id=1890537 (I've the feeling it could be), but if it's the case, we've some profiles in this bug which are showing that the `AndroidIU (JVM)` thread is doing a lot of things when almost nothing is done on the Gecko side (or pdf.js). I wonder if the stacks ending with `org.mozilla.fenix.FenixApplication.onTrimMemory` could indicate that the OS doesn't have enough memory or something like that and we're trying in Gecko to release some memory but it takes too much time, and then the OS spends too much time to empty the event queue containing the MotionEvent.