[frs] sorry to do this, but here is a crash report

Questions and discussion about building and using Max for Live devices
Post Reply
Surreal
Posts: 560
Joined: Wed May 17, 2006 1:18 am

[frs] sorry to do this, but here is a crash report

Post by Surreal » Mon Sep 21, 2009 11:43 am

from the apple window. i have no idea where crash pack would be...but max hung and then ableton hung.

[crash log removed - Friedemann]

Friedemann
Posts: 425
Joined: Mon Jun 28, 2004 10:47 am
Location: Ableton Headquarter

Re: sorry to do this, but here is a crash report

Post by Friedemann » Mon Sep 21, 2009 12:33 pm

Hi,

the crash packs are created on the Desktop when starting Live the next time after a crash and should be emailed to mfl-beta@ableton.com

Best, Friedemann
Friedemann Schautz
schautz@ableton.com

Surreal
Posts: 560
Joined: Wed May 17, 2006 1:18 am

Re: [frs] sorry to do this, but here is a crash report

Post by Surreal » Mon Sep 21, 2009 3:20 pm

i have received this notice a few times without a crash pack

Live unexpectedly quit while working on the live set "Unnamed Live Set"

is unexpected quitting different from crashing or have i botched something?

Friedemann
Posts: 425
Joined: Mon Jun 28, 2004 10:47 am
Location: Ableton Headquarter

Re: [frs] sorry to do this, but here is a crash report

Post by Friedemann » Mon Sep 21, 2009 3:28 pm

No, that's all the same. It looks like a problem with our crash reporting code. But you can also email the crash report that the Mac OS generates to mfl-beta@ableton.com

Best, Friedemann
Friedemann Schautz
schautz@ableton.com

Surreal
Posts: 560
Joined: Wed May 17, 2006 1:18 am

Re: [frs] sorry to do this, but here is a crash report

Post by Surreal » Mon Sep 21, 2009 5:22 pm

can do!

gil_
Posts: 3
Joined: Thu Sep 10, 2009 10:32 am

Re: [frs] sorry to do this, but here is a crash report

Post by gil_ » Tue Sep 22, 2009 4:28 pm

talking about max crashes, I have a crash nearly each time I want to save my MFL patch with Max5.1 ,
I suspect this might be due to OS X 10.4.11 ( because of the libSystem.B.dylib message) , I'm not using 10.5 on that machine yet

as a work around, I have to edit the patch as a non MFL patch (i.e. a normal max patch) , then copy it in a new MFL patch so as to be able to save it, but the next time I am editing it from Live to Max5.1, it will crash when I'm trying to save it ... it's not a big patch, but I have a few abstractions inside

is it a known bug ?

thx !

g

----------------------------

here is the begining of the crashed thread

OS Version: 10.4.11 (Build 8S2167)
Report Version: 4

Command: MaxMSP
Path: /Applications/Max5.1.0a1/MaxMSP.app/Contents/MacOS/MaxMSP
Parent: WindowServer [60]

Version: 5.1.0a1 (39951) (5.1.0a1)

PID: 422
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0 Crashed:
0 libSystem.B.dylib 0x900022f0 strlen + 16
1 com.cycling74.MaxMSP 0x0002f93e advise_explain + 200
2 com.cycling74.MaxAPI 0x0460e453 advise_explain + 59
3 com.cycling74.MaxAudioAPI 0x17ce4797 liveowner_showdialog + 233
4 com.cycling74.MaxMSP 0x000b44df object_method_typed + 127
5 com.cycling74.MaxMSP 0x00208eff maxservercontext_object_method_typed(_maxservercontext*, symbol*, long, atom*, atom*) + 167
6 com.cycling74.MaxMSP 0x000b44df object_method_typed + 127
7 com.cycling74.MaxMSP 0x0020863e maxservercontext_processconnection(_maxservercontext*) + 66
8 com.cycling74.MaxMSP 0x002086e0 maxserver_serviceconnections + 80
9 com.cycling74.MaxMSP 0x0020735d maxremote_readmessage + 161
10 com.cycling74.MaxMSP 0x00207a6a remote_object_method_typed + 302
11 com.cycling74.MaxAPI 0x04627839 remote_object_method_typed + 71
12 com.cycling74.MaxAudioAPI 0x17ce3ff6 liveowner_dorawsave + 415
13 com.cycling74.MaxAudioAPI 0x17ce40bb liveowner_windsaveas + 43
14 com.cycling74.MaxMSP 0x000b44df object_method_typed + 127
15 com.cycling74.MaxMSP 0x001c5ae2 patcherview_command(_patcherview*, symbol*, long, atom*, atom*) + 96
16 com.cycling74.MaxMSP 0x000b44df object_method_typed + 127
17 com.cycling74.MaxMSP 0x0015a236 jmenu_process + 562
18 com.cycling74.MaxMSP 0x000dc982 interface_process + 24
19 com.cycling74.MaxMSP 0x00012621 app_eventhandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 169
20 com.apple.HIToolbox 0x92e054d7 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
21 com.apple.HIToolbox 0x92e04b7c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
22 com.apple.HIToolbox 0x92e0bf7c SendEventToEventTarget + 56
23 com.apple.HIToolbox 0x92e8cadd SendHICommandEvent(unsigned long, HICommand const*, unsigned long, unsigned long, unsigned char, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 405
24 com.apple.HIToolbox 0x92ec08c6 ProcessHICommandWithContextAndModifiers + 60
25 com.apple.HIToolbox 0x92ec0864 SendMenuItemSelectedEvent + 128
26 com.apple.HIToolbox 0x92ec077c FinishMenuSelection(MenuData*, MenuData*, MenuResult*, MenuResult*, unsigned long, unsigned long, unsigned long, unsigned char) + 122
27 com.apple.HIToolbox 0x92ea54c5 MenuSelectCore(MenuData*, Point, double, unsigned long, OpaqueMenuRef**, unsigned short*) + 515
28 com.apple.HIToolbox 0x92ea4f66 MenuSelect + 100
29 com.cycling74.MaxMSP 0x002c59a9 juce::MouseClickHandlerProc(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 195
30 com.apple.HIToolbox 0x92e054d7 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
31 com.apple.HIToolbox 0x92e04b7c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
32 com.apple.HIToolbox 0x92e0bf7c SendEventToEventTarget + 56
33 com.apple.HIToolbox 0x92e0c999 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2587
34 com.apple.HIToolbox 0x92e0588e DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2044
35 com.apple.HIToolbox 0x92e04b7c SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
36 com.apple.HIToolbox 0x92e0bf7c SendEventToEventTarget + 56
37 com.cycling74.MaxMSP 0x002c7448 juce::juce_dispatchNextMessageOnSystemQueue(bool) + 580
38 com.cycling74.MaxMSP 0x002d0ed4 juce::MessageManager::dispatchNextMessage(bool, bool*) + 68
39 com.cycling74.MaxMSP 0x002d0f7e juce::MessageManager::runDispatchLoop() + 34
40 com.cycling74.MaxMSP 0x002cf8f9 juce::JUCEApplication::main(juce::String&, juce::JUCEApplication*) + 605
41 com.cycling74.MaxMSP 0x002cf9d3 juce::JUCEApplication::main(int, char**, juce::JUCEApplication*) + 125
42 com.cycling74.MaxMSP 0x001db5b6 main + 76
43 com.cycling74.MaxMSP 0x000057b6 _start + 216
44 com.cycling74.MaxMSP 0x000056dd start + 41

gil_
Posts: 3
Joined: Thu Sep 10, 2009 10:32 am

MFL patch name too long crashes Max5.1

Post by gil_ » Wed Sep 23, 2009 10:51 am

regarding my previous crash report , I think I have solved it by simply shortening the name of the MFL patch and Max5 is not crashing anymore :D ,
so it looks like this was the problem, the name was 23 characters long before (with the .amxd extension) , it seems there is a limit to the length of MFL patch name :o .

g

stefan-tiedje
Posts: 219
Joined: Thu Sep 17, 2009 3:50 pm
Location: Berlin

Re: [frs] sorry to do this, but here is a crash report

Post by stefan-tiedje » Sun Oct 04, 2009 9:56 am

After sending in my reports coming across this post, as I also have that problem with a bigger (huge?) patch. But mine has a very short name (four characters). I doubt its the name, I guess you are changing your patch also all the time...;-)
Les Ondes Mémorielles-----x---
--____-----------|----------|----
--(_|_ ----|\-----|-----()--------
-- _|_)----|-----()---------------
----------()----------TJ Shredder
http://tjshredder.wordpress.com/

Post Reply