In bug 1618560 comment 7 and later, I debugged an issue where in our code to profile multiple JVM threads, `ThreadGroup.enumerate` doesn't include the main thread during the `test_feature_java.js`. test. I was unable to reproduce locally on both physical and virtual devices (x86_64 on Android 7.0, same as test harness). I landed a workaround that fixes the test and code but may still be covering a bug either in the production code (where we don't see all available threads) or the test harness (where it's configured differently from how users experience the app). This bug is to document this issue and perhaps one day investigate.
Bug 1760716 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In bug 1618560 comment 7 and later, I debugged an issue where in our code to profile multiple JVM threads, `ThreadGroup.enumerate` doesn't include the main thread during the `test_feature_java.js` test when run in automation. I was unable to reproduce locally on both physical and virtual devices (x86_64 on Android 7.0, same as test harness). I landed a workaround that fixes the test and code but may still be covering a bug either in the production code (where we don't see all available threads) or the test harness (where it's configured differently from how users experience the app). This bug is to document this issue and perhaps one day investigate.