Drag-and-drop of (large amount of) text on address bar causes 7s hang on the parent process
Categories
(Firefox :: Address Bar, defect, P2)
Tracking
()
People
(Reporter: mayankleoboy1, Assigned: mbeier)
References
(Regression)
Details
(Keywords: perf, regression, Whiteboard: [sng][search-performance])
Attachments
(3 files)
STR:
- Open the attached testcase in the browser
- Select all the text (Ctrl+A) and then drag-and-drop the selected text to the address bar
AR: The whole browser freezes (for 7 seconds)
ER: Not so
Profile: https://share.firefox.dev/3LJu4xg
Bisection:
Bug 1841869 - entering "abc @xyz.[TLD]" in address bar opens a prompt regarding loading "xyz.[TLD]" instead of searching for "abc @xyz.[TLD]" on the default search engine.r=adw
Differential Revision: https://phabricator.services.mozilla.com/D198196
Reporter | ||
Comment 1•1 year ago
|
||
Reporter | ||
Updated•1 year ago
|
Reporter | ||
Comment 2•1 year ago
|
||
Reporter | ||
Updated•1 year ago
|
Reporter | ||
Comment 3•1 year ago
|
||
Maybe the regex used in the regressor bug needs to be more specialized? Or an upper bound is needed on the total time spent in searching? Or not do the search in parent process at all.
Comment 4•1 year ago
|
||
Set release status flags based on info from the regressing bug 1841869
Comment 5•1 year ago
|
||
The regex should definitely be applied to a partial string, or more specialized.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 6•1 year ago
|
||
Set release status flags based on info from the regressing bug 1841869
Updated•11 months ago
|
Comment 7•11 months ago
|
||
The Performance Impact Calculator has determined this bug's performance impact to be medium. If you'd like to request re-triage, you can reset the Performance Impact flag to "?" or needinfo the triage sheriff.
Platforms: [x] Windows [x] macOS [x] Linux
Impact on browser: Causes noticeable jank
Configuration: Rare
[x] Able to reproduce locally
Updated•10 months ago
|
Assignee | ||
Comment 8•8 months ago
|
||
Updated•8 months ago
|
Updated•8 months ago
|
Comment 10•8 months ago
|
||
bugherder |
Updated•8 months ago
|
Updated•8 months ago
|
Comment 11•8 months ago
|
||
The patch landed in nightly and beta is affected.
:mbeier, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox134
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Updated•8 months ago
|
Comment 12•7 months ago
|
||
Reproducible on a 2024-12-12 Nightly build on Windows 10.
Verified as fixed on Firefox Nightly 135.0a1 on Windows 10, Ubuntu 22, macOS 14.
Updated•6 months ago
|
Description
•