Closed
Bug 1517440
Opened 7 years ago
Closed 7 years ago
"Find in files" in debugger for string with lot of occurrences requires gigabytes of memory (leak)
Categories
(DevTools :: Debugger, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: gwarser, Unassigned)
Details
Attachments
(1 file)
|
32.82 KB,
application/gzip
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0
Steps to reproduce:
- open clean firefox profile
- switch to "Firefox Privacy Notice" tab ( https://www.mozilla.org/en-US/privacy/firefox/ )
- open dev tools (F12)
- switch to debugger tab
- ctrl+shift+f for "Find in files"
- type dot ("." without quotes)
- enter
Actual results:
Memory starts rising fast (~200MB/s), filling my 4GB ram + 4GB swap.
Dialog can appear:
>A script on this page may be busy, or it may have stopped responding. You can stop >the script now, open the script in the debugger, or let the script continue.
>
>Script: resource://devtools/shared/bas…rc/components/ProjectSearch.js:100
First happened to me on https://duckduckgo.com/?q=property&t=ffsb&ia=web with search for "fe" (without quotes) but after some time started to "behave" (needed "only" 1GB of memory) and then I also tried on other pages (for example https://duckduckgo.com) and different strings "fe", "fn", "return".
Memory report attached. Can be incomplete because it's nearly impossible to switch tabs and save.
2,561.15 MB (100.0%) -- explicit
├──2,319.83 MB (90.58%) ── heap-unclassified
Comment 1•7 years ago
|
||
Not sure the debugger is the right place ? (still better than untriaged)
Component: Untriaged → Debugger
Product: Firefox → DevTools
Comment 2•7 years ago
|
||
Thanks for filing. This is currently being tracked here https://github.com/devtools-html/debugger.html/issues/7629.
The Debugger UI is a bit different than other projects in that it is primarily developed in https://github.com/devtools-html/debugger.html.
Updated•7 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•