When I destroy rope constraint, then destroy both attachments, the rope constraint is still physically there (even though the instances are nowhere to be seen).
Setting Enabled to false before calling :destroy() fixes the issue.
But I assume the constraint might still be lingering somewhere in memory so this should be fixed.
Thanks for this bug report! We’ll look into this.
We have a fix for this, but it won’t be available for at least two weeks. Temporarily use constraint.enabled = false before calling :Destroy(). There should not be issues with memory leaks, the constraint is properly destroyed if enabled is set to false and destroy is called right after. If only Destroy is called, the constraint is eventually deleted - not immediate but it still happens.
http://devforum.roblox.com/t/major-roblox-update-for-4-28-16-0-241-0-73233/24602/28?u=chefdeletat