Brennon Bortz

I've got a patch that won't function properly. Well, it works like a dandy on my Mac, but it's a no-go on the PC. Who'd-a thunk it, right?

The error occurs anytime I click on the "Number of voices" umenu. There's some scripting that goes on with this object, but I can't tell what the problem is, as it works just fine on the Mac! No errors are reported to the Max window.

Problem is, I can't even get a dump log out of it on the PC. Obviously, I can't get one on the Mac because I can't get it to crash there. The Windows event log only shows the following error:

Faulting application max.exe, version 5.0.5.36470, faulting module max.exe, version 5.0.5.36470, fault address 0x00242645.

For more information, see Help and Support Center at 

http://go.microsoft.com/fwlink/events.asp.

Lots of help, huh? I'm sorry to have attached a .zip file, but without the necessary abstractions, and scripting, it won't run at all. If anyone could open her up and even just send me the dump log I would be VERY grateful.

I've got a patch that won't function properly.  Well, it works like a dandy on my Mac, but it's a no-go on the PC.  Who'd-a thunk it, right?

The error occurs anytime I click on the "Number of voices" umenu.  There's some scripting that goes on with this object, but I can't tell what the problem is, as it works just fine on the Mac!  No errors are reported to the Max window.

Problem is, I can't even get a dump log out of it on the PC.  Obviously, I can't get one on the Mac because I can't get it to crash there.  The Windows event log only shows the following error:

Event Type:	Error
Event Source:	Application Error
Event Category:	None
Event ID:	1000
Date:		1/20/2009
Time:		3:47:02 AM
User:		N/A
Computer:	BBORTZ
Description:
Faulting application max.exe, version 5.0.5.36470, faulting module max.exe, version 5.0.5.36470, fault address 0x00242645.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 6d 61 78   ure  max
0018: 2e 65 78 65 20 35 2e 30   .exe 5.0
0020: 2e 35 2e 33 36 34 37 30   .5.36470
0028: 20 69 6e 20 6d 61 78 2e    in max.
0030: 65 78 65 20 35 2e 30 2e   exe 5.0.
0038: 35 2e 33 36 34 37 30 20   5.36470 
0040: 61 74 20 6f 66 66 73 65   at offse
0048: 74 20 30 30 32 34 32 36   t 002426
0050: 34 35 0d 0a               45..    

Lots of help, huh?  I'm sorry to have attached a .zip file, but without the necessary abstractions, and scripting, it won't run at all.  If anyone could open her up and even just send me the dump log I would be VERY grateful.

patch-blowing-up

Sorry...this is an updated .zip file--ignore the first one. Changed a couple of things, but the error still occurs. Also, I should note that the main patch to open is "plugin2.maxpat".

Sorry...this is an updated .zip file--ignore the first one.  Changed a couple of things, but the error still occurs.  Also, I should note that the main patch to open is "plugin2.maxpat".

On 20 janv. 09, at 04:59, Brennon Bortz wrote:

> Sorry...this is an updated .zip file--ignore the first one. Changed 

> a couple of things, but the error still occurs. Also, I should note 

> that the main patch to open is "plugin2.maxpat".

Looking quickly at your js code on mac here is a few observation:

#1 in additiveUmenu.js: I'm not certain that calling 

this.patcher.getnamed() in your global code is safe. The patcher might 

not be initialized yet, and this call might not be successful. You can 

either do that in a loadbang method or just do it each time you need 

to get the MaxObj which shouldn't cause much performance penalty.

#2 in newPatcher.js: What is that supposed to do? Why do you need a 

while loop for that, a simple is enough as there can only be one 

while(a = this.patcher.getnamed("houdiniButton")){

#3 in newPatcher.js: there's no way to know if a patcher created with 

new Patcher() is still valid (once you freed it with the wclose 

message), you might want to have a variable which stores if the 

patcher is currently open or not and make sure that you don't create 

the patcher twice or that you don't free it twice.

> Sorry...this is an updated .zip file--ignore the first one.  Changed  
> a couple of things, but the error still occurs.  Also, I should note  
> that the main patch to open is "plugin2.maxpat".

#1 in additiveUmenu.js: I'm not certain that calling  
this.patcher.getnamed() in your global code is safe. The patcher might  
not be initialized yet, and this call might not be successful. You can  
either do that in a loadbang method or just do it each time you need  
to get the MaxObj which shouldn't cause much performance penalty.

#2 in newPatcher.js: What is that supposed to do? Why do you need a  
while loop for that, a simple is enough as there can only be one  
object named "houdiniButton".

     while(a = this.patcher.getnamed("houdiniButton")){
         this.patcher.remove(a);
     }

#3 in newPatcher.js: there's no way to know if a patcher created with  
new Patcher() is still valid (once you freed it with the wclose  
message), you might want to have a variable which stores if the  
patcher is currently open or not and make sure that you don't create  
the patcher twice or that you don't free it twice.

That's a lot of help, Emmanuel. I appreciate it!

That's a lot of help, Emmanuel.  I appreciate it!


Patch blowing up