I suspect the error is caused by too many PlayerAdded connections, please Roblox investigate this.
Place where the error occurs: [MERMAID!] Lost Currents [Alpha] - Roblox
Expected behavior
Please let us know what needs to be done to fix this problem, or fix it on Roblox side, please.
yeah ive been seeing this too in my game
Our analytics and error logs are swamped with this error… 
This error only started recently this past Roblox version change and we haven’t made any changes that could cause this to start happening.
Got the same issue.
This just started happening today for me as well. Everytime a player joins.
same thing is happening to me to :
also (idk if this is related to this bug) but has anyone also gotten a problem where some scripts that use run service frequently dont work as intended in studio specifically? for some reason those scripts work perfectly fine in the actual game tho.
No more like the polar opposite for my game works in studio fails in game.
Had the same issue. Fixed for me now
Still happens for me.
Your casual C++ error, they made a change and they are probably manipulating a null pointer at some point in the code, they’ll quickly see it
This error has crippled our game’s console and error logging systems. It’s being absolutely spammed and clogs up the console, preventing us from seeing important printed info and actual errors from in-game scripts.
@Hooksmith @Kepzun Can this be triaged? We simply cannot wait until next week for this to be fixed.
See the thread below with many more affected users:
This error has been breaking are systems.
can anyone tell me, is this a roblox error, or do we have to fix it ourselves, I can’t test my game with other testers without breaking the game 
It’s a roblox issue nothing we can do since it an error for the roblox garbage collector I think.
Thank you for the reports.
We have a team looking into the issue right now.
It’s an error that occurs at the engine level. Aside from being patient so that they sort it out, you can’t do anything about it, and it is not due to a faulty script you wrote
This error can occur in different contexts, especially when manipulating a null pointer, with smart pointers that C++ offers. They may be attempting to cast a weak pointer to something else, and unfortunately a change in the engine causes this cast to be performed on null in an unsafe manner.
The on-call team expects to have solved the issue by now. It should stop occurring in a few minutes.
Do we know why this issue happened?
Confirming this is resolved across all live game servers and Studio sessions.
Thanks so much for promptly dealing with this! Much appreciated.
