Simon O'Rorke

: 8.2.0 (The bug does not occur in 8.1.11.)

 objects is closed, message 'freeobject: 

 is an 8-character hex string, is shown, once for each 

 object, on the Max console. Example message: 'freeobject: 15b7fcf0: bad object'. Apart from the console messages on closing, the patcher works normally, so far as I can tell.

1) Create or open a patcher containing two 

 is an 8-character hex string, is shown twice on the Max console.

Max Version: 8.2.0 (The bug does not occur in 8.1.11.)

When a patcher containing one or more vst~ objects is closed, message 'freeobject: hhhhhhhh: bad object', where hhhhhhhh is an 8-character hex string, is shown, once for each vst~ object, on the Max console. Example message: 'freeobject: 15b7fcf0: bad object'. Apart from the console messages on closing, the patcher works normally, so far as I can tell.

1) Create or open a patcher containing two vst~ objects.

Message 'freeobject: hhhhhhhh: bad object', where hhhhhhhh is an 8-character hex string, is shown twice on the Max console. 

 Bug Report
Max Version: 8.2.0 (The bug does not occur in 8.1.11.)
Operating System: Windows 10
Summary
When a patcher containing one or mor

bug-report-'freeobject-…-bad-object'-when-a-patcher-containing-a-vst~-object-is-closed

@Simon, you're not alone! I reported this bug as well a couple days ago. They acknowledged it and are working on a fix.

Thanks for the update, Rafal. If you reported it via the forum, can you put a link here please? But I did search before reporting the bug. So my guess is you reported the bug by email or the "Report a Problem" web form. I've done that in the past but decided to try posting to the forum with a "Bugs/Issues" tag this time.

Thanks for the update, Rafal.  If you reported it via the forum, can you put a link here please?  But I did search before reporting the bug.  So my guess is you reported the bug by email or the "Report a Problem" web form.  I've done that in the past but decided to try posting to the forum with a "Bugs/Issues" tag  this time.

Yeah I used the bug reporting form. Let's hope this to get solved soon!

This has been fixed in version 8.2.1. See "vst~: eliminated freeobject error and potential memory leak" in 

This has been fixed in version 8.2.1.  See "vst~: eliminated freeobject error and potential memory leak" in the release notes.  Thanks.

Bug Report: 'freeobject: … bad object' when a patcher containing a vst~ object is closed