MaxMsp Bug, huge patch. freeobject : 3a145cc0 : bad object

Apr 10, 2008 at 8:56am

MaxMsp Bug, huge patch. freeobject : 3a145cc0 : bad object

Hello/
I have a problem since few weeks, and it makes me very crazy.
It’s about maxmsp. I made a Big patch which is a complete sequencer with 7 tracks, controlled by a Lemur. each track has volume, pan, pitch and other way of playing with the sample, automated and recorded in coll object. there is patherns, and a playlist.

Since few weeks, the program crash sometimes, very quickly, with no ERROR message printed in the max window. It happens with or without the LEMUR controlling the sequencer, and not on a specific action. It seems that the crash doen’t happen when audio is turned off. i make it play the song, patherns, but without audio on. Does it mean that it’s a probleme with an Audio object only ?

yesterday, i had a message printed in the max window
= freeobject : 3a145cc0 : bad object
This means something for someone ????

My theory is that the crashs that happen sometimes come from this corrupt object, but i don’t know how to find it.
I work on a brand new MacBook Pro 2.4 Ghz, 4 Go SDRAM, on 10.5.2

In the patch i am only using simple objects, and a delay (ej.vdb~) and the freeverb~. Not exotic objects.
Jitter is installed too, even if i don’t use it for the moment.

Here is what is printed in the max window when i launch the patch =
Jitter 1.6.3 installed
MXJ System CLASSPATH:
/Applications/MaxMSP 4.6/Cycling ’74/java/lib/jitter.jar
/Applications/MaxMSP 4.6/Cycling ’74/java/lib/jode-1.1.2-pre-embedded.jar
/Applications/MaxMSP 4.6/Cycling ’74/java/lib/max.jar
MXJClassloader CLASSPATH:
/Applications/MaxMSP 4.6/Cycling ’74/java/classes/
Jitter Java support installed
jazzserver ‘jazzserver’ created
jazzserver ‘jazzserver’ open port 8000…
freeverb~ v1.2.2

I am lost in the crachs, and i use every day the sequencer. :-(

thanks for your help.
Yohan

#36836
Apr 10, 2008 at 2:39pm

Does it work ok without the networking objects?

-A

#126576
Apr 10, 2008 at 4:48pm

On Mac OS the Crash Log is often informative. You might want to post it.

#126577
Apr 10, 2008 at 8:34pm

I have the same problem, whenever patches get (really) big, there is an increasing chance that max will suddenly crash, seemingly without any clear reason. The crash reports (I don’t have one ready now) indicate that the crash happened in a very basic object like trigger or pak or a scheduler tick method.

Btw, I usually send these crash reports to apple, I was wondering, do those arrive at cycling ’74 headquarters somehow? If not, would it make sense to send them somewhere else? Note though, that would be at an average rate of about 5 a day.

Mattijs

#126578
Apr 10, 2008 at 9:47pm

hello and thanx for your help.

Andrew = unfortunatly, it will not be easy for me to work without the ethernet object. i’ve got a lot of them, in every patch and subpatchs. i would have do it an other way. I f the problem is not solved these days, i’ll use your advise, and try without them.

Matijis, I really hope there’s a solution to that kind of problem, cause i can’t live with that crashes. I will use the patch on stage, Live, and a crash every 2 songs is not .. apropriate.
But you gave me a good tip, i remember that i place some pak object and i will see if there’s a difference without them.

Peter, by Crash Log, do you mean the repport that appears right after the crash ? i had one this evening =
I really don’t understand how to find the source of the crash in this file. a little help ?
Here we gO/

Process: MaxMSP [223]
Path: /Applications/MaxMSP 4.6/MaxMSP.app/Contents/MacOS/MaxMSP
Identifier: com.cycling74.MaxMSP46
Version: ??? (4.6.3)
Code Type: X86 (Native)
Parent Process: launchd [78]

Date/Time: 2008-04-10 23:28:04.050 +0200
OS Version: Mac OS X 10.5.2 (9C2028)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000a10d6264
Crashed Thread: 0

Application Specific Information:

Java information:
Version: Java HotSpot(TM) Client VM (1.5.0_13-119 mixed mode)
Virtual Machine version: Java HotSpot(TM) Client VM (1.5.0_13-119) for macosx-x86, built on Nov 25 2007 06:10:34 by root with gcc 4.0.1 (Apple Inc. build 5465)
Exception type: Bus Error (0xa) at pc=0x0007001c

Current thread (0x17d01340): JavaThread “AWT-AppKit” [_thread_in_native, id=-1606778976]
Stack: [0xbf800000,0xc0000000)
Java Threads: ( => current thread )
0x17d0ec50 JavaThread "AWT-Shutdown" [_thread_blocked, id=17858048]
0x17d0b8e0 JavaThread “Low Memory Detector” daemon [_thread_blocked, id=17628160]
0x17d0aeb0 JavaThread “CompilerThread0″ daemon [_thread_blocked, id=17624576]
0x17d0a8c0 JavaThread “Signal Dispatcher” daemon [_thread_blocked, id=17620480]
0x17d0a600 JavaThread “Surrogate Locker Thread (CMS)” daemon [_thread_blocked, id=17616896]
0x17d09d10 JavaThread “Finalizer” daemon [_thread_blocked, id=17610752]
0x17d09910 JavaThread “Reference Handler” daemon [_thread_blocked, id=17607168]
=>0x17d01340 JavaThread “AWT-AppKit” [_thread_in_native, id=-1606778976]
Other Threads:
0x17d09060 VMThread [id=17528832]
0x17d0c4e0 WatcherThread [id=17631744]

VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None

Heap
par new generation total 4032K, used 1048K [0x1c270000, 0x1c670000, 0x1ca70000)
eden space 3968K, 26% used [0x1c270000, 0x1c376358, 0x1c650000)
from space 64K, 0% used [0x1c650000, 0x1c650000, 0x1c660000)
to space 64K, 0% used [0x1c660000, 0x1c660000, 0x1c670000)
concurrent mark-sweep generation total 61440K, used 0K [0x1ca70000, 0×20670000, 0x2c270000)
concurrent-mark-sweep perm gen total 8192K, used 2775K [0x2c270000, 0x2ca70000, 0×30270000)

Virtual Machine arguments:
JVM args: -Xincgc -Xms64m -Xmx256m
Java command:
launcher type: generic

Thread 0 Crashed:
0 com.cycling74.MaxMSP46 0x0007001c wind_eventhandler + 170 (window.c:3313)
1 com.cycling74.MaxMSP46 0x00026bff max_doeventtimerproc + 101 (main.c:677)
2 com.cycling74.MaxMSP46 0x00026ccb max_eventtimerproc + 35 (main.c:724)
3 com.apple.CoreFoundation 0x91c4db5e CFRunLoopRunSpecific + 4494
4 com.apple.CoreFoundation 0x91c4dd18 CFRunLoopRunInMode + 88
5 com.apple.HIToolbox 0x943766a0 RunCurrentEventLoopInMode + 283
6 com.apple.HIToolbox 0x943764b9 ReceiveNextEventCommon + 374
7 com.apple.HIToolbox 0x943d51fe _AcquireNextEvent + 58
8 com.apple.HIToolbox 0x943d395b RunApplicationEventLoop + 207
9 com.cycling74.MaxMSP46 0×00027854 app_run + 52 (main.c:1519)
10 com.cycling74.MaxMSP46 0x00027afe main + 680 (main.c:416)
11 com.cycling74.MaxMSP46 0x00002ba2 _start + 216
12 com.cycling74.MaxMSP46 0x00002ac9 start + 41

Thread 1:
0 libSystem.B.dylib 0x93297a46 semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x932c9daf _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x932cb633 pthread_cond_timedwait_relative_np + 47
3 …ple.CoreServices.CarbonCore 0x908da92a TSWaitOnConditionTimedRelative + 246
4 …ple.CoreServices.CarbonCore 0x908da70a TSWaitOnSemaphoreCommon + 422
5 …ple.CoreServices.CarbonCore 0x9090b4a8 TimerThread + 74
6 libSystem.B.dylib 0x932c8c55 _pthread_start + 321
7 libSystem.B.dylib 0x932c8b12 thread_start + 34

Thread 2:
0 libSystem.B.dylib 0x932979e6 mach_msg_trap + 10

#126579
Apr 10, 2008 at 10:15pm

Quote: yopaii wrote on Thu, 10 April 2008 23:47
—————————————————-

This is where you should find the source of the crash:

> Thread 0 Crashed:
> 0 com.cycling74.MaxMSP46 0x0007001c wind_eventhandler + 170 (window.c:3313)
> 1 com.cycling74.MaxMSP46 0x00026bff max_doeventtimerproc + 101 (main.c:677)
> 2 com.cycling74.MaxMSP46 0x00026ccb max_eventtimerproc + 35 (main.c:724)
> 3 com.apple.CoreFoundation 0x91c4db5e CFRunLoopRunSpecific + 4494
> 4 com.apple.CoreFoundation 0x91c4dd18 CFRunLoopRunInMode + 88
> 5 com.apple.HIToolbox 0x943766a0 RunCurrentEventLoopInMode + 283
> 6 com.apple.HIToolbox 0x943764b9 ReceiveNextEventCommon + 374
> 7 com.apple.HIToolbox 0x943d51fe _AcquireNextEvent + 58
> 8 com.apple.HIToolbox 0x943d395b RunApplicationEventLoop + 207
> 9 com.cycling74.MaxMSP46 0×00027854 app_run + 52 (main.c:1519)
> 10 com.cycling74.MaxMSP46 0x00027afe main + 680 (main.c:416)
> 11 com.cycling74.MaxMSP46 0x00002ba2 _start + 216
> 12 com.cycling74.MaxMSP46 0x00002ac9 start + 41
>

But in this case there doesn’t seem to be any specific object involved. Otherwise there would be something like com.cycling74.counter 0x0007001c count + 170 (counter.c:12) in the uppermost lines (that would mean that the counter object did something wrong).

FWIW: This is exactly the kind of crash report I get when max crashes. That’s right, I recognize this without even comparing with an actual crash report. I have seen these lines very often.

Mattijs

#126580
Apr 10, 2008 at 10:18pm

Btw I modified your post on the forum, it got very long. Please attach a long text like this in a zip next time. I attached it here.

Mattijs

#126581
Apr 13, 2008 at 12:50am

Quote: Mattijs wrote on Thu, 10 April 2008 13:34
—————————————————-
> I have the same problem, whenever patches get (really) big, there is an increasing chance that max will suddenly crash, seemingly without any clear reason. The crash reports (I don’t have one ready now) indicate that the crash happened in a very basic object like trigger or pak or a scheduler tick method.
>

I was having similar issues recently. No idea if this will help anyone, but FWIW:

I have a patch with thousands of pattrs (don’t ask) and I was using a monome to control some of the pattr state. That required the use of a udpsend/receive to talk to the pattrs. It seemed I started having crash issues when I added the monome support. So I took out the udpsend/receive and the crashes stopped. I ended up putting the monome stuff in a completely separate patch and use the [pattrmarker] object to communicate with the main patch. Now it works fine… well, opening the patch takes 10-20 seconds and maxes out my CPU, but otherwise it’s fine ;)

It may be possible I changed something else but I’m pretty sure the removal of the udpsend/receive fixed the issue for me. I’m sure there are lots of reasons crashes happen in big patches though. I don’t have the crash logs anymore but I looked at them and the error was for some random object that had nothing to do with the real issue.

Sometimes a well placed [deferlow] also seems to fix some serious issues, but I don’t have a good sense of when to use it.

#126582
Jul 10, 2008 at 9:35pm

I’m back. HELLO

after several weeks of search on my crash problem, i’m still at the same point. I erased a lot of thing in my patch (half), i change ALL JazzClient objects by ONE udpreceive, and i still have these unbelievable crash. the sequencer is playing, i let it like that, and suddendly..crash report.
I begin to give up, and tell my self “you have to live with this crash all your life” :-)
Here is an other crash report. if someone understand something in this file, PLEASE, give me your help/

YOHAN

#126583

You must be logged in to reply to this topic.