Forum Discussion
Have feedback on the memory/CPU usage on Edge? We're Listening!
Allison_Pastewka
Even without any tabs opened Edge on Android locks the frequency to max on little cores (sdm660) with an overall CPU usage of around 50% and I don't even know what is it doing in background.
I've tried blocking Background Sync and Notifications from Site Permissions, I've also tried blocking JavaScript but all in vain.
The only way to bring it back to normal is deleting all user data of the Edge app and start over as freshly installed app but it least for a while until it starts misbehaving again. This brings a bit hit to battery life while using edge in background or foreground. Android will eventually kill it if it stays in background for too long but for the time it stays there it noticeably eats a chuck of remaining battery charge.
I'm using a Nokia 7 Plus running Android 9.0.
I don't know if it will help debugging but I've attached a "dumpsys activity". Edge's activity name is "u0a258" as seen in the "top" command screenshot.
If more logs are needed let me know, I would happily provide them.
MicrosoftCoddy Hi, Thank you for the detailed feedback. We would like to help resolve this with you. Could you pleases share this feedback with logs from within the Android app to help us continue to troubleshoot? Thank you, Andrea
- Here is the logcat. First is full output, second one is filtered by chromium process because the first one is crowded with other useless outputs.
Did you meant another type of Android logs ?
Edit: I may have misunderstood the request. I've now posted a feedback from within Edge Android but it doesn't allow to attach logs in the form.- Andrea_MLThank you Coddy. We will start the investigation. The logs are collected when you go into the app tap on Overflow menu (… on the footer) > Send feedback . check "Send device information"
- Sorry I haven't replied.
Yes, the box was ticked when I've shared the feedback from within the Edge browser app.
I hope that and the dumpsys and logcat I've shared in my previous two post will suffice.
I've just noticed that filtering by the PID which has the high CPU usage instead of activity (u0aXXX) in the dumpsys output I get those two:
* Googlequicksearchbox package
* Google firebase activity
With the latter being know to causes undesirable effects around app developers. TBN I'm not an app developer but I've read forums while trying to debug something else and bumped into discussions about firebase integration in apps and wrong configurations/calls that would result in misbehaving. Those are my 2 cents.