withakay

If Max crashes and the reason is unknown (thus not repeatable) is there some place to report such things?

I can't report a bug exactly because I can't work out the causes of the crashes but they happen frequently. When I work in Max I now expect it to crash if I use it long enough. In eight hours use 2-4 crashes is quite normal, do other people see crashes this frequently?

FWIW I am using a Mac Pro with OS X 10.6.8 and Max 6.0.3 (although all versions of Max 6 have behaved similarly for me).

Getting pretty frustrated with it, so any help or advice is appreciated.

If Max crashes and the reason is unknown (thus not repeatable) is there some place to report such things?
I can't report a bug exactly because I can't work out the causes of the crashes but they happen frequently. When I work in Max I now expect it to crash if I use it long enough. In eight hours use 2-4 crashes is quite normal, do other people see crashes this frequently?

Getting pretty frustrated with it, so any help or advice is appreciated.


reporting-crashes

When this happens, typically I will first post the postmortem stack trace for the crashed thread along with a description of what I was doing on the forum to see if it is a known issue. If nobody has any idea from that, then I email it to support. I have found them to be very responsive.

This time I edited an abstraction that was being using inside a patch loaded into a poly object and hit save.

Similar events have lead up to previous crashes, but I can't work out how to repeat them.

This time I edited an abstraction that was being using inside a patch loaded into a poly object and hit save.
Similar events have lead up to previous crashes, but I can't work out how to repeat them.

Crash report: http://pastebin.com/NZuty2u3


. This is supposed to work since 6.0.2 but maybe it doesn't... Let's hope c74 people will have a look (it's easier for them if you could provide a crashing patch!)

It seems to be caused by a receive~ inside a poly~. This is supposed to work since 6.0.2 but maybe it doesn't... Let's hope c74 people will have a look (it's easier for them if you could provide a crashing patch!)

I frequently have a dozen of crashes a day… The last ones seemed to be associated with the use of vst~. But like you, I can't work out to repeat them and I'm pretty noob with max, so my patches are rather simple. No poly objects, no jitter etc

I've sent a report to support for the first crashes (those just after the release of max6) but they answered that it could be due to CNMAT externals (the only one used was OSC-route wich seems pretty straightforward), that's all. Since this one, I didn't send any report until a few days ago. It was too frustrating and I sent the patch with a crash log. But no answer at all… The worst is I'm not enough sure of my knowledge to say if it's my programmer skills or the bugginess of Max the culprit. I will stop to use it for now, too much irritating…

Concerning crashes, it's the same here !
I frequently have a dozen of crashes a day… The last ones seemed to be associated with the use of vst~. But like you, I can't work out to repeat them and I'm pretty noob with max, so my patches are rather simple. No poly objects, no jitter etc
I've sent a report to support for the first crashes (those just after the release of max6) but they answered that it could be due to CNMAT externals (the only one used was OSC-route wich seems pretty straightforward), that's all. Since this one, I didn't send any report until a few days ago. It was too frustrating and I sent the patch with a crash log. But no answer at all… The worst is I'm not enough sure of my knowledge to say if it's my programmer skills or the bugginess of Max the culprit. I will stop to use it for now, too much irritating…


If I can repeat it I will certainly post the patch.

And another one. This time I had just left Max open whilst I looked some stuff up on teh intarwebz. This is really getting me down :(

If you are getting unexpected crashes, you should email support at cycling 74 dot com. Please include the following:

- the crashing patch (please try to simplify the patch as much as possible)

- any other relevant information (regression, expected results, notes, etc)

If you have emailed and haven't gotten a response in a 3-4 business days, then it is likely that your email has gotten caught in a spam filter. Please resend, as we answer every email we receive.

If you are getting unexpected crashes, you should email support at cycling 74 dot com.  Please include the following:

- operating system
- computer model
- exact version of Max installed
- the crashing patch (please try to simplify the patch as much as possible)
- numbered steps to reproduce the crash
- if on Mac, a crash report
- any other relevant information (regression, expected results, notes, etc)

If you have emailed and haven't gotten a response in a 3-4 business days, then it is likely that your email has gotten caught in a spam filter.  Please resend, as we answer every email we receive.

"- numbered steps to reproduce the crash"

^^^ That is the main reason I have not emailed in any reports, I can't *make* Max crash on purpose... :(

Also I am having huge problems with frequent MFL crashes. Often it crashes the whole Ableton suite. Usually everything is fine until I do not open the MAX device editor. After that the average crash frequency is kind of 1 every 2 hours or worse. These crashes are NOT reproducible. So I was not able to send some useful information to Cycling74's support. No particular patch of mine is more prone to crashes than others. Max patches outside Ableton Live are having crashes too, but a lot less. Usually I do not use externals, just javascript and rarely java.

Bug report is a matter I know very well. My company is working with a bunch of beta testers around the world and they have to follow strict rules. Maybe Cycling74 should implement a log feature as Ableton did - would make things easier.

my system: computer: HPE-340it, Intel i7 CPU 860 @2.8GHz, RAM 16GB 1333 MHz

MAX version 6.07, Ableton Live Suite 8.3.4

Also I am having huge problems with frequent MFL crashes. Often it crashes the whole Ableton suite. Usually everything is fine until I do not open the MAX device editor. After that the average crash frequency is kind of 1 every 2 hours or worse. These crashes are NOT reproducible. So I was not able to send some useful information to Cycling74's support. No particular patch of mine is more prone to crashes than others. Max patches outside Ableton Live are having crashes too, but a lot less. Usually I do not use externals, just javascript and rarely java.
Bug report is a matter I know very well. My company is working with a bunch of beta testers around the world and they have to follow strict rules. Maybe Cycling74 should implement a log feature as Ableton did - would make things easier.
my system: computer: HPE-340it, Intel i7 CPU 860 @2.8GHz, RAM 16GB 1333 MHz
MAX version 6.07, Ableton Live Suite 8.3.4


reporting crashes