Forums > MaxMSP

strange max window messages

February 5, 2009 | 9:16 pm

Hi,
I noticed this in the max window– I dont know when it occurred because the window was hidden. Anyone know whats going on here?

zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (updatecommand): corrupt object
zgetfn (edclose): corrupt object


February 10, 2009 | 12:40 am

The zgetfn means that one object tried to internally send a message (updatecommand/edclose) to an object which doesn’t exist anymore. Lots of objects send these sorts of messages, esp. anything that has an editor window. In any case, it’s more than likely just a cosmetic problem.

Are you using any third party objects?

-Ben


February 10, 2009 | 10:22 am

>Are you using any third party objects?

I dont think so. I think it happened after a crash, and then I relaunched the patch which had unsaved data that was lost due to the crash; I think its the crash report I sent to you (Case 45143) last week. I quit and relaunched a few times and each time I relaunched these error messages became fewer, until they disappeared altogether… creepy.

The only other thing I can tell you is that this message appeared with the < zgetfn> message:

method wclose called on invalid object

It was repeated many times. With the particular patch in question this message always appears (but only once) because I send a message to close a subpatch window on loadbang before its opened, so its an error that is harmless that I’m already aware of, but on this one occasion it kept repeating itself as if stuck in some loop.
It hasn’t again happened since.
T


July 5, 2010 | 12:53 pm

hi there,
I got the same error message in a patch where I would really like everything to work smooth and clean…
so, even if it is a mere cosmetic problem, is there a way of clearing it?

thanx in advanx
tom


July 5, 2010 | 1:24 pm

Which version of Max do you use? Do you use any third party external? could you post a patch? Thanks.


Viewing 5 posts - 1 through 5 (of 5 total)