Frequent slow typing/input in Google Docs due to CC
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
People
(Reporter: robwu, Unassigned)
References
(Blocks 1 open bug)
Details
After 3 weeks of browsing, I am encountering severe input lag when trying to type in Google Docs.
When I view about:processes, I see that the process is shared between Gmail and Google Docs, if it is relevant.
When I open a new Docs tab (which somehow ends up in a separate process), I don't see input lag.
Profile: https://share.firefox.dev/3EpWuf3
Note the screenshots. I am typing "test" repeatedly with a constant speed. At the 2 second mark, what I type is not rendered by Docs any more. Around the 5.5 second mark, my typed input is replayed fast and the rendered text on the screen catches up with what I typed. The profiler shows that GC has been running all the time until then. My system is powerful and has plenty of free RAM when this happens.
Note that this is consistently reproducible when I get into this state: if I go to the affected tab and start typing, then I will quickly hit the "I type but Docs seems to be non-responsive" state.
|
Reporter | |
Comment 1•28 days ago
|
||
Extra info: the Doc that I am typing in is only one simple page (so this bug is different from bug 1488435). The other Docs in the same processes have only a few pages in total. I cannot rule out that there have been other larger docs in the same process. In any case, the process hosting these Google sites is "only" 4.4 GB. In contrast, my main process is 9.4 GB, and I have 64 GB RAM in total.
|
||
Comment 2•28 days ago
|
||
This is the cycle collector, not the garbage collector. Typically, this is a sign of a leak, probably a window leak, in the given process.
You said this has been "3 weeks of browsing". What branch and version are you using? We fixed bug 1939295 about 2 weeks ago so this is likely a dupe.
|
|
||
Updated•28 days ago
|
|
|
Reporter | |
Comment 3•28 days ago
|
||
The build on which I am experiencing this is 136.0a1 20250107165124.
When I visit about:memory, I do indeed see 1.8 GB of ghost windows, which consists of a handful of documents that I opened and closed before. These do indeed have many pages (al together probably in the order of 100, maybe 200 pages).
1 GB of the other "window-objects" memory usage is with Gmail and Docs.
730 MB is with non-window objects, 480 heap-unclassified, 134 MB images, followed by other small stuff.
We fixed bug 1939295 about 2 weeks ago so this is likely a dupe.
Given the ghost windows in my about:memory report, bug 1939295 looks like a likely candidate.
However, I would not be surprised if the same issue would still be observed if I did NOT close the docs. In that case, I suppose that this specific report would then be part of bug 1488435?
|
|
||
Comment 4•28 days ago
|
||
(In reply to Rob Wu [:robwu] from comment #3)
However, I would not be surprised if the same issue would still be observed if I did NOT close the docs. In that case, I suppose that this specific report would then be part of bug 1488435?
If you update your browser and continue to experience hangs, and get profiles that don't show the CC being the cause of them, then yes it would be something else. I have seen some people complaining about slowness on Google Docs recently where the profiles are in JS.
Anyways, I'm sure this is just bug 1939295. If you update to a more recent version and continue to experience problems you are probably best off filing a new bug.
Description
•