search in source code stalls
Categories
(Core :: Performance, defect)
Tracking
()
People
(Reporter: info, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/109.0
Steps to reproduce:
Open a lengthy HTML page and then open the HTML source code view.
Then starting a search for a string in there, like "<strong>"
Actual results:
When I start typing the first letter in the search, the search already starts, stalling the app for a minute with a apple spinning wheel of death (and I have a MacBookProM1 Ultra, one of the fastest) and obviously starting a search and highlighting of that single letter, which was not intended.
Then the second letter of my search is entered, and the whole thing starts again, now searching for the 2 letter string.
Expected results:
The application waits a little before the search starts to see the users' intention to add more letters to the search string first.
|
||
Updated•2 months ago
|
|
||
Updated•2 months ago
|
|
||
Comment 1•2 months ago
|
||
I tried using View Source on a couple of large Wikipedia pages (e.g. History of Western Civilization), and the search seemed quite responsive (on an older Intel MacBook).
Could you give a specific example of a "lengthy HTML page" where you're seeing this issue? I wonder if it's related to more factors than just the length of the page.
|
Reporter | |
Comment 2•2 months ago
|
||
Hi Jonathan, thank you for your prompt reply. Impressing, I did not expect one.
Well, the issue turns out to go a different direction than I thought. I have had the effect since weeks. But now starting the browser fresh, everything's OK, now that you ask. (And I bet, tomorrow it's back. I had not written the report if the problem was not severe and frequently.)
It's like this: You have a pain for weeks, then you finally decide to see the doctor… and the pain is gone.
You are right: Maybe I am facing a memory problem, or so, which indirectly makes that slow?
Those pages were going slow, but not now:
https://finnie-and-friends.de/ueber-uns/
https://www.hanse-aesthetic.de/brustvergroesserung/
I do not have fancy plugins, here's my list:
- 1Password
- BookMacster Sync
- Clear Cache
- Cookiebro
- Copy PlainText
-LanguageTool - Long Screenshot
- NsLookup - Find DNS Records
- ReviewMeta.com Review Analyzer
- Security Web Auditing
- SingleFile
- Web Developer
Can you leave the report open for some days? I need to re-check after I had the browser open for a few hours work. I might have overlooked something obvious.
Have a nice weekend, and thanks for your support!
|
||
Comment 3•2 months ago
|
||
If you see the issue again, could you perhaps provide a performance profile using https://profiler.firefox.com/
"Upload Local Profile" gives you a shareable link.
That profile might reveal if it is for example some of the addons causing the issue.
I have this issue too and it's killing me. As a web developer, I'm constantly looking at the source and searching for stuff.
Here is my Profiler link:
|
|
||
Comment 5•1 month ago
|
||
(In reply to Thomas from comment #4)
I have this issue too and it's killing me. As a web developer, I'm constantly looking at the source and searching for stuff.
Here is my Profiler link:
It looks like you have some form of accessibility tools turned on, and that is hurting performance really badly. The new "Cache the World" architecture discussed in a recent blog post may help, but unfortunately I believe it isn't quite ready on macOS yet.
(In reply to Jonathan Kew [:jfkthame] from comment #5)
(In reply to Thomas from comment #4)
I have this issue too and it's killing me. As a web developer, I'm constantly looking at the source and searching for stuff.
Here is my Profiler link:
It looks like you have some form of accessibility tools turned on, and that is hurting performance really badly. The new "Cache the World" architecture discussed in a recent blog post may help, but unfortunately I believe it isn't quite ready on macOS yet.
I disabled all my extensions, restarted Firefox, re-enabled them, restarted Firefox and the issue has gone away. Not sure why that'd help, but it did.
Description
•