Typing in not work in address bar some times and them make force quit
Categories
(Firefox :: Address Bar, defect)
Tracking
()
People
(Reporter: mohsen.noor, Unassigned, NeedInfo)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36
Steps to reproduce:
Sometimes when I try to type an address in the address bar it has lag (delay) or
And then stop accepting characters
Actual results:
The force quit window appears in Ubuntu
Expected results:
the text must appear smoothly
Comment 1•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Address Bar' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•1 year ago
|
||
Mohammad Mohsen, can you please try and reproduce with a new and empty profile (https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems#w_6-create-a-new-firefox-profile)? As I am not able to reproduce it on ubuntu 24.04 using Firefox build 133.0 and 134.0b4.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 4•1 year ago
|
||
One of the profiles seem to point to a Snap release, the other one is not.
Maybe you could try an official Mozilla distribution from https://www.mozilla.org/en-US/firefox/linux/? does this one work?
| Reporter | ||
Comment 5•1 year ago
|
||
Marco Bonardo, I disabled and removed my extensions, and the problems have gone every think is normal
| Reporter | ||
Comment 6•1 year ago
|
||
You may find all of my extensions in file Firefox_bug.txt. The first file I updated
Comment 7•1 year ago
|
||
Interesting, the ones thay may be relevant are GNOME Shell integration and Dastyar Personal Assistant in your newtab.
I don't know what exactly they do, it would be nice to test and see how they may break the urlbar, as it may be related to the omnibox WebExtension api.
Comment 8•1 year ago
|
||
The severity field is not set for this bug.
:adw, could you have a look please?
For more information, please visit BugBot documentation.
Comment 9•1 year ago
|
||
Hi Mohammad, could you try re-enabling the disabled WebExtensions one by one until you are able to narrow down which one of them could be causing the performance regression?
Additionally, it'd be helpful once the regression is encountered again, to provide us a performance profile: https://profiler.firefox.com/
Updated•1 year ago
|
Comment 10•1 year ago
|
||
Feel free to reopen the report if the bug returns or you have answers to the question in comment 9
Description
•