MAX Crashing

andytodd.msp

Hi guys, I'm having an issue with a patch of mine which seems to keep crashing and giving me the 'max has stopped working' dialogue box.

I copied the crash log..

Problem signature:
Problem Event Name:    APPCRASH
Application Name:    Max.exe
Application Version:    6.0.8.0
Application Timestamp:    509bfc3e
Fault Module Name:    sfplay~.mxe
Fault Module Version:    6.0.8.0
Fault Module Timestamp:    509c03bc
Exception Code:    c0000005
Exception Offset:    00005d37
OS Version:    6.1.7601.2.1.0.256.48
Locale ID:    2057
Additional Information 1:    0a9e
Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
Additional Information 3:    0a9e
Additional Information 4:    0a9e372d3b4ad19135b953a78882e789

I'm gussing its a problem with one of my sfplay objects, but i cant think what!

Any ideas?

Andy

Peter Castine

That's not the whole crash log. The stack trace for the crashed thread would be interesting.

What would be even more helpful is the patch (if possible, stripped-down).

If the patch is crashing immediately when it's opened, you'll need to hold down Shift and Command while the patch is opening (this pevents loadbang and loadmess objects from triggering).

andytodd.msp

Hi Peter, how do I get a stack trace?

Andy

Andrew Pask

You can't really get them on Windows.

Try tracking it down a bit - is it a particular file?

Also, you might try updating to 6.1.3

If you can figure out what it is and it still crashes in 6.1.3, send a report to support

Cheers

-A

Peter Castine

Sorry, that was obviously a Windows crash log, not sure why I was thinking otherwise. So I guess you're stuck with plan B (stripping down your patch to try to localize the problem).

Although Andrew's suggestion of updating to 6.1.3 has many merits, if for some reason you can't do that, you would still have the option of posting the problem part of the patch here. There are other folks using 6.0.x, and you might get some feedback indicating whether it's an obscure bug in some object you're using or if there may be some system problem you're running up against. And some kind soul or other might be able to confirm whether the problem persists in 6.1.3.

Good luck!