1854407 - Memory leak

Status: RESOLVED INCOMPLETE

(Core :: Graphics, defect, P2)

Description

[xircambyses]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/117.0

Comment 1

[xircambyses]

Attachment: memory-report.json.gz

Comment 2

[xircambyses]

Attachment: about:support

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

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

Comment 4

[Emilio Cobos Álvarez (:emilio)]

Can you elaborate? Any steps to reproduce? The parent process is using ~2 gigs of memory which seems high (mostly graphics), but other than that it seems mostly-fine for that many processes?

Comment 5

[Bob Hood [:bhood]]

Might be related to Bug 1847453 (both are using AMD GPUs), but that one is on Windows.

Comment 6

[Sotaro Ikeda [:sotaro]]

Attachment 9354364 [details] has a lot of process names. I wonder if opening a lot of Tabs with WebGL/accelerated Canvas2D might consume a lot of memory.

:lsalzman, could it possible to happen?

Comment 7

[Lee Salzman [:lsalzman]]

(In reply to Sotaro Ikeda [:sotaro] from comment #6)

Attachment 9354364 [details] has a lot of process names. I wonder if opening a lot of Tabs with WebGL/accelerated Canvas2D might consume a lot of memory.

:lsalzman, could it possible to happen?

Most of the memory usage I see is in WebRender, not in WebGL or AC2D. And given the number of tabs, the memory usage doesn't seem unreasonable?

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

A needinfo is requested from the reporter, however, the reporter is inactive on Bugzilla. Given that the bug is still UNCONFIRMED, closing the bug as incomplete.

For more information, please visit BugBot documentation.