Typing in Fenix url bar crashes
Categories
(Fenix :: Search, defect, P2)
Tracking
(firefox120 wontfix, firefox121 wontfix, firefox122 wontfix, firefox123 fixed, firefox124 fixed)
People
(Reporter: jib, Unassigned)
References
(Regression)
Details
(Keywords: crash, regression)
Attachments
(4 files)
Steps to reproduce
- Open a new tab in Firefox for Android
- Make sure DuckDuckGo is selected as search engine
- Click on url bar to enter text
- Enter 'a'
Expected behavior
- Autocomplete of something starting with 'a'
Actual behavior
- Screen goes black after a second and Fenix appears to restart
Device information
- Firefox version: 121
- Android device model: Samsung S9
- Android OS version: 10
Any additional information?
- Nothing in about:crashes
- Does not happen with Google selected as search engine
- Does not happen in Firefox 119 release
| Comment hidden (obsolete) |
|
Reporter | |
Comment 2•1 year ago
|
||
Process org.mozilla.fenix:tab27 (pid 28971) has died: fore BTOP(279,146)
|
||
Comment 3•1 year ago
|
||
I'm seeing the same issue on Nightly since about a week ago. Navigation works fine, but typing in the address bar reliably locks up my phone after 5-10 seconds, until Firefox gets killed. I'm not using DDG.
I think it's going out of memory.
|
|
||
Comment 4•1 year ago
|
||
More info: it also happens in Private Mode and with my add-ons disabled.
I can confirm this exact same bug since the update to 120.0 (Build #2015986298) 039de7ef85+
Firefox crashes without crash log, when directly typing into search bar or opening link from suggestions. After restart, opened tab is gone, but no crash report is logged. Launcher seemingly crashes as well and restarts after a couple seconds.
|
||
Comment 6•1 year ago
|
||
Same thing happens to me, but with any search engine. I've even turned off all auto-suggestion options, but just typing something at all in the address bar and waiting kills firefox and the launcher regardless.
|
|
Reporter | |
Comment 8•1 year ago
|
||
I'm seeing it with any search engine as well.
|
|
Reporter | |
Comment 9•1 year ago
|
||
WIN DEATH: Window{e782a8 u0 org.mozilla.fenix/org.mozilla.fenix.App} from the attached log doesn't sound good, but also doesn't look like a regular crash.
|
||
Comment 10•1 year ago
|
||
Thanks for reporting this Jan-Ivar! The logs don't tell me much about the cause of process death. It could be that there is some filtering happening?
Concurrently, you could get to the crashes list to get the crash info by clicking on the three-dot menu -> Settings -> About Firefox -> Crashes. That might be helpful for us to figure out the cause.
|
|
||
Comment 11•1 year ago
|
||
I'm almost certain it's an OOM because it locks up my phone. It doesn't show up under Crashes.
|
||
Comment 12•1 year ago
|
||
Can confirm the OOM. This is the output of free -m during a crash. At around 17:44:38 I opened the first page, which did not crash. At 17:44:54 I opened the second page, which crashed and took the logger with it:
Time Mem Total Mem Used Mem Free Mem Shared Mem Buffers Buffers Free Buffers Cache Swap Total Swap Used Swap Free
2023-12-13 17:44:27 3648 3522 126 12 12 3510 138 1806 1770 35
2023-12-13 17:44:28 3648 3522 126 12 12 3510 138 1806 1770 35
2023-12-13 17:44:29 3648 3522 126 12 12 3510 138 1806 1770 35
2023-12-13 17:44:30 3648 3523 125 12 12 3511 137 1806 1770 35
2023-12-13 17:44:31 3648 3477 171 12 12 3465 183 1806 1768 37
2023-12-13 17:44:32 3648 3526 122 12 13 3513 135 1806 1779 27
2023-12-13 17:44:33 3648 3527 121 12 12 3514 133 1806 1780 26
2023-12-13 17:44:34 3648 3523 125 13 12 3510 138 1806 1806 0
2023-12-13 17:44:35 3648 3523 125 14 13 3509 139 1806 1726 80
2023-12-13 17:44:36 3648 3519 129 29 31 3487 161 1806 1756 49
2023-12-13 17:44:37 3648 3510 138 13 51 3459 189 1806 1760 46
2023-12-13 17:44:38 3648 3579 69 13 59 3520 128 1806 1739 66
2023-12-13 17:44:39 3648 3473 175 10 62 3411 237 1806 1631 174
2023-12-13 17:44:40 3648 3536 112 10 54 3482 166 1806 1515 291
2023-12-13 17:44:41 3648 3599 49 9 52 3546 102 1806 1380 425
2023-12-13 17:44:42 3648 3540 108 7 45 3494 154 1806 1579 227
2023-12-13 17:44:43 3648 3413 235 7 67 3346 302 1806 1651 155
2023-12-13 17:44:44 3648 3420 228 7 76 3343 305 1806 1645 160
2023-12-13 17:44:45 3648 3442 206 7 83 3359 289 1806 1643 163
2023-12-13 17:44:46 3648 3521 127 7 82 3438 209 1806 1650 156
2023-12-13 17:44:48 3648 3477 171 9 77 3399 249 1806 1586 219
2023-12-13 17:44:49 3648 3405 243 8 77 3327 321 1806 1584 221
2023-12-13 17:44:50 3648 3524 124 24 78 3445 203 1806 1594 212
2023-12-13 17:44:51 3648 3522 126 24 79 3442 206 1806 1593 213
2023-12-13 17:44:52 3648 3521 127 24 79 3441 207 1806 1591 215
2023-12-13 17:44:53 3648 3456 192 24 80 3376 272 1806 1583 223
2023-12-13 17:44:54 3648 3521 127 8 80 3440 208 1806 1577 228
2023-12-13 17:44:55 3648 3465 183 8 80 3384 264 1806 1579 226
2023-12-13 17:44:56 3648 3578 70 8 79 3498 150 1806 1596 210
2023-12-13 17:44:57 3648 3559 89 6 37 3521 127 1806 1694 111
2023-12-13 17:44:58 3648 3632 16 5 4 3627 21 1806 1806 0
The Firefox crashlogs are empty.
|
|
||
Comment 13•1 year ago
|
||
My apologies, the column titles were wrong. Buffers Free, is buffers used, and buffers cache is buffers free:
Time Mem Total Mem Used Mem Free Mem Shared Mem Buffers Buffers Used Buffers Free Swap Total Swap Used Swap Free
2023-12-13 17:44:27 3648 3522 126 12 12 3510 138 1806 1770 35
2023-12-13 17:44:28 3648 3522 126 12 12 3510 138 1806 1770 35
2023-12-13 17:44:29 3648 3522 126 12 12 3510 138 1806 1770 35
2023-12-13 17:44:30 3648 3523 125 12 12 3511 137 1806 1770 35
2023-12-13 17:44:31 3648 3477 171 12 12 3465 183 1806 1768 37
2023-12-13 17:44:32 3648 3526 122 12 13 3513 135 1806 1779 27
2023-12-13 17:44:33 3648 3527 121 12 12 3514 133 1806 1780 26
2023-12-13 17:44:34 3648 3523 125 13 12 3510 138 1806 1806 0
2023-12-13 17:44:35 3648 3523 125 14 13 3509 139 1806 1726 80
2023-12-13 17:44:36 3648 3519 129 29 31 3487 161 1806 1756 49
2023-12-13 17:44:37 3648 3510 138 13 51 3459 189 1806 1760 46
2023-12-13 17:44:38 3648 3579 69 13 59 3520 128 1806 1739 66
2023-12-13 17:44:39 3648 3473 175 10 62 3411 237 1806 1631 174
2023-12-13 17:44:40 3648 3536 112 10 54 3482 166 1806 1515 291
2023-12-13 17:44:41 3648 3599 49 9 52 3546 102 1806 1380 425
2023-12-13 17:44:42 3648 3540 108 7 45 3494 154 1806 1579 227
2023-12-13 17:44:43 3648 3413 235 7 67 3346 302 1806 1651 155
2023-12-13 17:44:44 3648 3420 228 7 76 3343 305 1806 1645 160
2023-12-13 17:44:45 3648 3442 206 7 83 3359 289 1806 1643 163
2023-12-13 17:44:46 3648 3521 127 7 82 3438 209 1806 1650 156
2023-12-13 17:44:48 3648 3477 171 9 77 3399 249 1806 1586 219
2023-12-13 17:44:49 3648 3405 243 8 77 3327 321 1806 1584 221
2023-12-13 17:44:50 3648 3524 124 24 78 3445 203 1806 1594 212
2023-12-13 17:44:51 3648 3522 126 24 79 3442 206 1806 1593 213
2023-12-13 17:44:52 3648 3521 127 24 79 3441 207 1806 1591 215
2023-12-13 17:44:53 3648 3456 192 24 80 3376 272 1806 1583 223
2023-12-13 17:44:54 3648 3521 127 8 80 3440 208 1806 1577 228
2023-12-13 17:44:55 3648 3465 183 8 80 3384 264 1806 1579 226
2023-12-13 17:44:56 3648 3578 70 8 79 3498 150 1806 1596 210
2023-12-13 17:44:57 3648 3559 89 6 37 3521 127 1806 1694 111
2023-12-13 17:44:58 3648 3632 16 5 4 3627 21 1806 1806 0
|
||
Updated•1 year ago
|
|
|
||
Comment 14•1 year ago
|
||
It seems to be connected to the amount of open tabs. I was able to get rid of the crash by closing lots of old tabs (from over 100 down to 59 currently) and disabling "Search synchronized tabs" (in Settings > Search > Address bar - Firefox Suggest).
|
|
||
Comment 15•1 year ago
|
||
Oh yes, I have infinite (*) open tabs.
(*) maybe not infinite, but close.
|
|
||
Comment 16•1 year ago
|
||
Me as well. But this worked before and should continue to work like it has in the past. We never break userspace, even IF they have a gazillion tabs open on their mobile.
|
||
Updated•1 year ago
|
|
|
Reporter | |
Comment 17•1 year ago
|
||
I only have 5 tabs and it still crashes every time.
(In reply to Jonathan Almeida [:jonalmeida] from comment #10)
Thanks for reporting this Jan-Ivar! The logs don't tell me much about the cause of process death. It could be that there is some filtering happening?
Yes it was filtered. Here's an unfiltered snippet right before the WIN DEATH.
Concurrently, you could get to the crashes list to get the crash info by clicking on the three-dot menu -> Settings -> About Firefox -> Crashes. That might be helpful for us to figure out the cause.
It says "No crash reports have been submitted".
|
|
||
Comment 18•1 year ago
|
||
I disabled tab search without closing any tabs and this still happens.
|
|
||
Comment 19•1 year ago
|
||
Fenix has recently received mozregression support so you could try that to see if you can reproduce this issue there, that would be a lot of help. It's new to me as well, but I'll try to find someone that can help in case we both get stuck. :)
(In reply to Jan-Ivar Bruaroey [:jib] (needinfo? me) from comment #17)
Yes it was filtered. Here's an unfiltered snippet right before the WIN DEATH.
Strange that there is no discernable information in there to the cause of the process being killed, so it's hard to share what is causing this (OOM) crash.
|
|
||
Comment 20•1 year ago
|
||
Of course it shows up in the logs.
12-18 19:19:40.296 811 811 I lowmemorykiller: Kill 'org.mozilla.fenix' (20836), uid 10248, oom_score_adj 0 to free 163012kB rss, 314700kb swap
12-18 19:19:40.296 811 811 I lowmemorykiller: Reclaimed 163012kB at oom_score_adj 0
12-18 19:19:40.296 811 811 I lowmemorykiller: Suppressed 41 failed kill reports
|
|
||
Comment 21•1 year ago
|
||
Fenix killed at 12-18 19:19:40.296 811 811 I lowmemorykiller: Reclaimed 163012kB at oom_score_adj 0.
|
||
Comment 22•1 year ago
•
|
||
Just a guess: It might be related to recently introcuded svg icon decoder which using coil-kt (bug 1821701).
It has been backport to 120.0.1 ( the version said in bug 1868108)
Update: Sorry, the date doesn't match this bug's descrption.
Coil-kt issue https://github.com/coil-kt/coil/issues/1349
Suggestion
- svg icon decoder should put desiredSize.maxsize into coil-kt's image request
- try { decode()} catch(OOM) in svg icon decoder
- make use of memorycache/diskcache of coil-kt image loader
|
|
||
Updated•1 year ago
|
|
|
Reporter | |
Comment 23•1 year ago
•
|
||
I tried mozregression on it a few days ago, but the problem didn't reproduce there. Open to ideas why that might be.
|
|
||
Comment 24•1 year ago
|
||
Laurențiu, it looks like from your logs that the FxSuggest is still enabled. Can you please check Secret Settings to see if you can disable it? If it's already disabled, could you try to toggle it on and the off again?
If that solves it or not, please post back.
|
|
||
Comment 25•1 year ago
|
||
It's still crashing, I can post another log later.
|
|
||
Comment 26•1 year ago
|
||
Laurențiu, that should be okay, but I have another theory if you could be willing to test it out for me?
Could you disable, one at a time, each suggestion source:
- History
- Bookmarks
- Synchronised tabs
If that does solves it for you, can you enable one of them and then see which one causes the OOM? Maybe even a combination.
I really appreciate your help, thanks!
|
|
||
Comment 27•1 year ago
|
||
I disabled Firefox Suggest in the secret settings and everything under Search, and it still crashes. I don't even have to open a new tab, it's enough to type something in the URL bar (there are no suggestions when I do that).
|
|
||
Comment 28•1 year ago
|
||
FWIW, I noticed this on November 10, but it might be 1-2 (?) days older, depending on how fast Play Store updates get installed.
|
|
||
Comment 29•1 year ago
|
||
Disabling Firefox Suggest on its own was not enough for me either. I had to close enough tabs as well to get it to work again. Now it works for me, but if I enable Firefox Suggest -> Synchronized tabs it OOMs again. I can enable all other Firefox Suggest options just fine, though.
|
||
Updated•1 year ago
|
|
||
Comment 30•1 year ago
|
||
thank you i disabled everything in the Search Settings now the problem has stopped however i can add that i have 6 Samsung phones including Galaxy S7 SM-G930U OFW but no matter how much i use firefox this ONLY happens on Galaxy S9 SM-G960U OFW.
|
||
Comment 31•1 year ago
|
||
Disabling everything in Search Settings also seemed to fix the issue for me. I then went back to try enabling them one-by-one and Synced Tabs seems to be the culprit.
Firefox
121.0 (Build #2015991663), 1955f8455f+
GV: 121.0-20231214155439
AS: 121.0
Firefox Suggest Disabled in Secret Menu
Galaxy Z Flip 5 (SM-F731U1)
Android 14.0 / OneUI 6.0
|
|
||
Comment 32•1 year ago
|
||
perhaps I spoke too soon. disabling just Synced Tabs suggestions stopped the easy, immediate repro but has not fixed it completely 😕
|
|
||
Updated•1 year ago
|
|
||
Comment 33•1 year ago
|
||
I also have been affected for about a month.
firefox nightly 123.0a1 (2024-01-06) LineageOS 18.1 (Android 11)
I could reproduce the issue even with all options in Parameters > Search disabled (no search suggestion, no bookmarks, no synced tabs, no nightly suggestions, no sponsored suggestions).
logcat also suggests the problem is OOM.
Note that symptoms are sometimes delayed. On the last occurence, I typed transputer, had time to click on the wikipedia result, and then read the introduction before it crashed.
I'm also using duckduckgo as search engine and currently have ~70 open tabs. If that's relevant, I'm using a custom firefox sync server.
|
|
||
Comment 34•1 year ago
|
||
I also had the problem with the search engine set to qwant to the problem is not duckduckgo-specific.
|
|
||
Comment 35•1 year ago
|
||
I also had the problem with the search engine set to google.
|
||
Comment 36•1 year ago
•
|
||
I've been seeing this for a few months using Nightly with Google search on my Google Pixel 6 Pro, I thought it was an Android 14 bug because I got that OS update around the same time but today I read on https://www.reddit.com/r/firefox/comments/1874lux/firefox_on_android_repeatedly_crashing_on_my/ that it's triggered by typing in the address bar and carefully avoiding typing in the address bar has made my Fenix way more stable.
I'm able to repro if there are ideas to try, and I can use the Firefox USB debugging if it's useful but I'm not very familiar with it.
Things I've tried that prevented the crash:
- Not typing in the address bar.
- Disabling History sync in the Mozilla account sync settings.
|
||
Comment 39•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Fenix::Search' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 40•1 year ago
|
||
This is probably a duplicate of Bug 1874522, and is likely caused by multiple concurrent conversion of (same) SVGs to likely unreasonably large bitmaps. See the linked bug for more details clarifying why do I think so.
|
||
Comment 41•1 year ago
•
|
||
Sarah, since this is an S2 and tracked for Fx123, should we consider getting somebody assigned?
|
||
Updated•1 year ago
|
|
||
Comment 42•1 year ago
|
||
I am guessing, this is a duplicate of Bug 1874522 as mentioned above and since that got fixed, we'd like this one to be retested with those builds as well?
One of the builds with the fix would be https://send.ephemeral.land/download/657310447d134ebf/#cO7Jy_sdgOyQZtVD41_nMg
|
|
||
Comment 43•1 year ago
|
||
:towhite, since you are the author of the regressor, bug 1821701, could you take a look?
For more information, please visit BugBot documentation.
|
||
Comment 44•1 year ago
•
|
||
As this appears very similar, I'm closing this bug as a dupe in favour of Bug 1874522. Please feel free to reach out if this is not the case.
|
|
||
Comment 45•1 year ago
|
||
The patch to fix this bug will be uplifted to version 123 shortly, any feedback on whether this bug is resolved or not would be super helpful.
|
|
Reporter | |
Comment 46•1 year ago
|
||
It's fixed for me (I'm on 124). Thanks!
|
|
||
Updated•1 year ago
|
|
|
||
Comment 47•1 year ago
|
||
Seems fixed for me too.
Description
•