Incorrect warning messages while debugging client code with breakpoint

Problem description

Incorrect warning messages appear while debugging client code with breakpoint on Studio. Sometimes the messages start to spam dozens if not hundreds of times making impossible to check my prints. Breakpoint operations (step into, etc) are extremely slow while those messages keep printing.

Problem happens when the module was moved from a server storage to a shared storage before it was used by the client.

Messages

The warning messages are always this two. I’m not sure if they always appear together but it looks like it.

  1. PrivateServerId cannot be checked on the client, please check on the server.
  2. PrivateServerOwnerId cannot be checked on the client, please check on the server.

Reproduction file

This messages don’t make any sense for two reasons. First, they never print if I don’t stop the code with a breakpoint. Second, they appear in code bases where the client never read PrivateServerId or PrivateServerOwnerId. To prove my point, there is a minimum reproduction place attached below to check this bug. In the place, I just move a dummy module from ServerScriptService to ReplicatedStorage. Then, I call the module from the client and stop on print("foo") because of a breakpoint. The message appear after 1-2 seconds.

When the problem started

Today. I’ve debugged a production game that didn’t have this problem last month and it also happened there. I didn’t edit the code of this game. I just added a breakpoint on the conditions that I explained above.

Let me know if you need any more details.

2022_06_01_BreakpointBug.rbxl (34.7 KB)

Hi Bachatronic,
After investigating this issue, this is related to the new Intuitive Lua Debugger Beta, which you may have been opted into. If you go into the Beta Features menu, find the Intuitive Lua Debugger entry, and uncheck it and restart Studio, you should no longer run into this issue. Please PM me if you are still running into this issue after taking those steps or weren’t using the Intuitive Lua Debugger Beta.

2 Likes

This topic was automatically closed after 11 hours. New replies are no longer allowed.