Script has a chance of not being disconnected when parent is destroyed via serverside

Bug Reports Engine Bugs
,
#1

I noticed my error analytics was full of errors and managed to get some of it to show up in studio for the first time ever.

There is a random chance of localscripts which were created on the clientside not being disconnected properly when the parent is destroye on the serverside.

A private message is associated with this bug report

2 Likes
#2

This sounds like it’s working as intended?

The server can’t destroy any object created by the client, because it doesn’t know it exists (unless I’m not understanding the bug?)

#3

The server is making the localscripts disconnect properly 99% of the time.

If it does work as intended, this behaviour should be very confusing.

#4

Thanks for the report! We’ll follow up when we have an update for you.

1 Like
#5

Oh the parent is destroyed, by the server - got it.

That should disconnect, although it could be related to a reference being held? I know parenting localscripts to nil used to be a way to avoid having exploiters delete them - not sure how much of that is still around.

#6

OP has confirmed that the issue is resolved. We believe it was fixed by an update about a month ago to how scripts deferred themselves. TL;DR: if you deferred a script in a loop, it could never be destroyed, even if it was yielding. If anyone encounters this issue in the future, please let us know!

2 Likes