Closed Bug 1833549 Opened 11 months ago Closed 2 months ago

memory leak with many structured-clone-holders with Kaspersky addon

Categories

(WebExtensions :: Developer Outreach, defect, P3)

Firefox 113
defect

Tracking

(Not tracked)

RESOLVED MOVED

People

(Reporter: ropelandremix, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Attached file memory-report.json.gz

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0

Actual results:

Nothing? I thought the most recent update would fix it but it hasn't. I read that the memory leak is because of a specific theme but i don't use themes so i'm... unsure. i'm not tech savvy either i'm sorry.

task manager shows cpu at 39% and memory are 4.5k

The Bugbug bot thinks this bug should belong to the 'Firefox::Theme' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Theme
Component: Theme → Performance
Product: Firefox → Core

This bug was moved into the Performance component.

:ropelandremix, 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 from about:memory and 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.

Flags: needinfo?(ropelandremix)

There are many possible causes of memory leaks in Firefox. We need more information to understand the problem. What has lead you to say that you are experiencing a memory leak? How much memory is your system using? Where are you seeing that? Does it happen quickly or slowly?

None of the processes in your report have super high memory usage, but there are a vast number of structured clone holders

Main process:
41.70 MB (08.90%) ── structured-clone-holder [12940]

Pinterest process:
196.44 MB (46.10%) ── structured-clone-holder [107618]

Google processes:
228.23 MB (57.70%) ── structured-clone-holder [125612]
83.41 MB (23.61%) ── structured-clone-holder [43853]
183.99 MB (55.75%) ── structured-clone-holder [103553]

Truity process:
226.39 MB (68.76%) ── structured-clone-holder [123858]

Maybe this is related to an addon, but I'm not sure if there's any way to tell from the memory report.

See Also: → 1769763
Summary: memory leak unrelated to themes → memory leak with many structured-clone-holders

(In reply to BugBot [:suhaib / :marco/ :calixte] from comment #2)

This bug was moved into the Performance component.

:ropelandremix, 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 from about:memory and 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.

Here you go: https://share.firefox.dev/3BEqBuS

Flags: needinfo?(ropelandremix)

(In reply to Andrew McCreight [:mccr8] from comment #3)

There are many possible causes of memory leaks in Firefox. We need more information to understand the problem. What has lead you to say that you are experiencing a memory leak? How much memory is your system using? Where are you seeing that? Does it happen quickly or slowly?

None of the processes in your report have super high memory usage, but there are a vast number of structured clone holders

Main process:
41.70 MB (08.90%) ── structured-clone-holder [12940]

Pinterest process:
196.44 MB (46.10%) ── structured-clone-holder [107618]

Google processes:
228.23 MB (57.70%) ── structured-clone-holder [125612]
83.41 MB (23.61%) ── structured-clone-holder [43853]
183.99 MB (55.75%) ── structured-clone-holder [103553]

Truity process:
226.39 MB (68.76%) ── structured-clone-holder [123858]

Maybe this is related to an addon, but I'm not sure if there's any way to tell from the memory report.

I only assumed memory leak since that was what google said when I tried to figure out what was wrong. I'm sorry, I don't know much about this sort of topic. In task manager when this starts to happen it shows 80% of my PC memory being used and a large chunk of it is from firefox (at the moment it's using 5k mb total).

I tried turning off some of my add-ons/extension to see if the problem would slow stop but it didn't seem to work. It happens slowly, but it seems to start freezing more when I open a google doc/sheet for the first time.

From the profile, I think the Kaspersky addon might be the problem. Can you please try disabling it and see if this stops or reduces the problem?

Flags: needinfo?(ropelandremix)

(In reply to Julien Wajsberg [:julienw] from comment #6)

From the profile, I think the Kaspersky addon might be the problem. Can you please try disabling it and see if this stops or reduces the problem?

Hello, sorry for the late response, but after disabling the Kaskersky addon the problem stopped. Thank you for your help and thank you to everyone who responded!

Flags: needinfo?(ropelandremix)
Component: Performance → Developer Outreach
Product: Core → WebExtensions
Summary: memory leak with many structured-clone-holders → memory leak with many structured-clone-holders with Kaskersky addon
Summary: memory leak with many structured-clone-holders with Kaskersky addon → memory leak with many structured-clone-holders with Kaspersky addon
Severity: -- → S4
Priority: -- → P3

The latest release of Firefox includes more details in the about:memory report. Could you re-enable the add-on, trigger the bug and generate a new dump from about:memory?

Blocks: webext-perf
Flags: needinfo?(ropelandremix)

Developer was reached out through AMO

Status: UNCONFIRMED → RESOLVED
Closed: 2 months ago
Resolution: --- → MOVED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: