160 new replies in 30 seconds?

[Helpful Tech Witch]

Browser, version and OS: 

Windows 10 20H2, chrome  89.0.4389.90

Steps to reproduce/what were you doing before it happened?

Opened one of the verefied actual gamer threads and went back a few pages

 

What happened?

about 30 seconds after i open one of the older pages, I got a 168 new replies mesage

 

What did you expect to happen?

To get a one new reply message (there was only one new post)

 

Link to a page where it happened, if applicable: 

Screenshots of the issue, if applicable: 

screenshot was copied to my clipboard (used win+shift+s) I copied the page link over it

Any other relevant details:

not really

 

If it's a cloudflare error, what was the ray ID from the bottom of the error page?

n/a

[LogicalDrm]

Considering thread had at least 175 new replies since my last visit 16h ago, I don't think this is issue with forum. What I think is that you have tab open, but it wasn't refreshing or pinging server. Which would have cause this once you activate the tab and see all the posts that had been done while it was inactive.

 

80 posts within 1h, so I doubt this is forum issue.

Edited March 24, 2021 by LogicalDrm

[Helpful Tech Witch]

56 minutes ago, LogicalDrm said:

 

Considering thread had at least 175 new replies since my last visit 16h ago, I don't think this is issue with forum. What I think is that you have tab open, but it wasn't refreshing or pinging server. Which would have cause this once you activate the tab and see all the posts that had been done while it was inactive.

 

I didn't have the tab open. I I don't think I had any ltt tabs open on any of my other devices.

[colonel_mortis]

There was a known bug with this, but I thought it had been fixed. If memory serves, the way to get that bug was to start on page x, then switch to the last page, then use your browser's back button to return to page x - does that match what you did?

[Helpful Tech Witch]

Just now, colonel_mortis said:

There was a known bug with this, but I thought it had been fixed. If memory serves, the way to get that bug was to start on page x, then switch to the last page, then use your browser's back button to return to page x - does that match what you did?

Possibly, though this was at like 12 hours ago. 

I think it was tho.