Cef.log grows extremely large due to ResizeObserver spam when Chat sidebar is visible in a Voice Channel

TeamSpeak 6 Client
, , ,
1

Client Version: 6.0.0-beta4
OS: Windows

Description

When joining a voice channel with the text chat sidebar open/visible, cef.log fills up at an extremely fast rate. In a single session, I observed 7,321 identical log entries resulting in a ~1.3 MB file. Over extended use this accumulates silently to enormous sizes with no warning or automatic cleanup.

I only discovered this issue indirectly — I was investigating why my drive had almost no free space left while trying to optimize my CS2 performance. A CPU-Z system report revealed my drive was down to around 1-2% free space. After digging around, large TS6 log files turned out to be among the culprits.

The log is flooded with the following message, repeated multiple times per second:

[INFO:CONSOLE] "ResizeObserver loop completed with undelivered notifications.", source: tsui://default/index.html#/connection8/channel4?mode=,Chat

Steps to Reproduce

  1. Open TeamSpeak 6
  2. Connect to a server
  3. Join a voice channel that has the text chat sidebar visible
  4. Observe cef.log growing rapidly (located at %AppData%\TeamSpeak\logs\cef.log)
  5. Click away to a different channel where the chat panel is not shown → log spam stops immediately

Expected Behavior

The ResizeObserver error should either not occur, or be handled/throttled internally without being written to the log repeatedly.

Actual Behavior

The error is logged continuously for as long as the chat sidebar is rendered, filling cef.log with thousands of identical entries. There is no log rotation or size cap, so this can grow to fill the drive completely without the user noticing.

Root Cause (analysis)

This appears to be a ResizeObserver feedback loop in the chat panel UI — a layout change triggers the observer, which triggers another layout change, creating a self-reinforcing loop. Chromium/CEF aborts the loop after each frame but logs a warning every time, and TS6 does not suppress, throttle, or rotate these messages.

Workaround

Manually closing the chat sidebar after joining a voice channel stops the spam. There is currently no built-in log size limit or rotation.

1 Like
2

Well, this is not fully correct, the log is rotated with every start of TeamSpeak, but I agree, this should not be logged (to file)…

Until this is properly fixed you can go into Settings → Chats and set Editing Toolbar Visibility to Hidden. I know this is not a nice solution, and some of those log lines will still show up, but the toolbar seams to be the main culprit spamming the log file.

2 Likes
3

Thanks for the report. This is fixed internally and will be part of the next update. As a workaround you can indeed use @Gamer92000 solution if the log spam is an issue.

6 Likes