Flooding: socket

[Nicolas]

Hi guys,

Is it ok? Just saw this in console:

26/10 20:54 [53952] - warn: Flooding detected! Calls : 101, Duration : 8414
26/10 20:54 [53952] - warn: [socket.io] Too many emits! Disconnecting uid : 1. Events : topics.markAsRead,topics.loadMore,topics.markAsRead,topics.loadMore,topics.markAsRead,topics.loadMore,topics.markAsRead,topics.loadMore,topics.markAsRead,topics.loadMore,topics.markAsRead,topics.loadMore,topics.markAsRead,topics.loadMore,topics.markAsRead,topics.loadMore,topics.markAsRead,topics.loadMore,topics.markAsRead,topics.loadMore

[julian]

Yes, that's normal. We have some code in NodeBB that disconnects clients who make too many socket calls too quickly, and this usually happens on reconnection, as socket.io will try the call many times.

[Nicolas]

I mean so many similar requests. (why would markAsRead will be called several times on the same topic with single post?)
I think something isn't right. I'm just staying on one page, and can watch how CPU consumption grows on my dev machine.

Endless scrolling script doesn't like presence of iframes in post?

[Nicolas]

Topics: too many emits · Issue #3793 · NodeBB/NodeBB

Reproducing: Create topic Have several embeds in the same time Page enters some sort of loop Console Output: 27/10 19:18 [55136] - warn: Flooding detected! Calls : 101, Duration : 5401 27/10 19:18 [55136] - warn: [socket.io] Too many emi...

GitHub (github.com)