excessive memory use
Categories
(Core :: Performance: General, defect)
Tracking
()
People
(Reporter: councilaccount, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
1.17 MB,
application/x-gzip
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36 OPR/107.0.0.0
Steps to reproduce:
n/a
Actual results:
n/a
Expected results:
n/a
Comment 1•1 year ago
|
||
Councilaccount, can you please provide more details to this issue? Thank you.
Updated•1 year ago
|
Comment 2•1 year ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Performance' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 3•1 year ago
|
||
From the attached memory report I didn't see the excessive memory usage.
Please provide more details, and if possible capture a profile with http://profiler.firefox.com/, upload it and share the link here.
Comment 4•1 year ago
|
||
This bug was moved into the Performance component.
:councilaccount, could you make sure the following information is on this bug?
- For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
✅ For memory usage issues, capture a memory dump fromabout:memoryand attach it to this bug.- Troubleshooting information: Go to
about:support, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.
If the requested information is already in the bug, please confirm it is recent.
Thank you.
Comment 5•1 year ago
|
||
Removing perf impact flag and adding to memory investigation meta bu - please continue to provide additional details to help us remedy any possible issues
Comment 6•1 year ago
|
||
If no update is provided issue will be closed. Thank you.
Comment 7•1 year ago
|
||
Redirect needinfos that are pending on an inactive user to the triage owner.
:fdoty, since the bug has recent activity, could you have a look please?
For more information, please visit BugBot documentation.
Comment 8•1 year ago
|
||
Moving this bug to inactive. If the issue persists or new information is made available, please open a new bug and reference this one. Thanks
Description
•