Forums > MIRA

Mira iPad crash report

July 18, 2013 | 8:31 am

Hello,

Mira crashes quite often here and a "Mira Unexpectedly Quit" message box appears on the iPad’s screen. However I cannot send any report because the "Send" / "Do not send" buttons do not react to touch.


July 18, 2013 | 10:54 am

Sorry about that. What are you doing when the crash happens? Are you working with a specific patch?


October 23, 2013 | 3:46 am

Hello,
I am also experiencing systematic crashes with Mira, especially when opening the second tab of mira.frame.help

here is the crash log beginning

Best regards
Roland

Process: Max [1140]
Path: /Applications/Max6/Max.app/Contents/MacOS/Max
Identifier: com.cycling74.Max
Version: 6.1.3 [69b6394] (6.1.3)
Code Type: X86-64 (Native)
Parent Process: launchd [198]
User ID: 502

Date/Time: 2013-10-23 12:36:31.319 +0200
OS Version: Mac OS X 10.8.5 (12F45)
Report Version: 10

Interval Since Last Report: 179752 sec
Per-App Interval Since Last Report: 64583 sec
Per-App Crashes Since Last Report: 3
Anonymous UUID: 8F5E79F0-A810-EA0A-EAC6-E1CD9880CB18

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0×0000000000000000

VM Regions Near 0:
–>
__TEXT 0000000100000000-0000000100677000 [ 6620K] r-x/rwx SM=COW /Applications/Max6/Max.app/Contents/MacOS/Max

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_c.dylib 0x00007fff903b1670 strlen + 16
1 libsystem_c.dylib 0x00007fff903ca9f6 __strcpy_chk + 27
2 com.cycling74.mira-frame 0x000000011524578f XEBGetResourceData + 294
3 com.cycling74.mira-frame 0x000000011525c3ad XEBEndpoint_HandleFunctionMaybeLock + 330
4 com.cycling74.mira-frame 0x000000011525e739 XEBEndpoint_Process + 172
5 com.cycling74.Max 0×0000000100008422 clock_execute + 39
6 com.cycling74.Max 0x0000000100033ebe sched_takepoll + 513
7 com.cycling74.Max 0x000000010001292d max_tick + 139
8 com.cycling74.Max 0x0000000100388cff juce::InternalTimerThread::callTimers() + 155
9 com.cycling74.Max 0x0000000100387beb juce::MessageManager::deliverMessage(juce::Message*) + 123
10 com.cycling74.Max 0x0000000100472d39 juce::AppDelegateRedirector::runLoopCallback() + 113
11 com.apple.CoreFoundation 0x00007fff93c3cb31 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
12 com.apple.CoreFoundation 0x00007fff93c3c455 __CFRunLoopDoSources0 + 245
13 com.apple.CoreFoundation 0x00007fff93c5f7f5 __CFRunLoopRun + 789
14 com.apple.CoreFoundation 0x00007fff93c5f0e2 CFRunLoopRunSpecific + 290
15 com.apple.HIToolbox 0x00007fff90bd0eb4 RunCurrentEventLoopInMode + 209
16 com.apple.HIToolbox 0x00007fff90bd0c52 ReceiveNextEventCommon + 356
17 com.apple.HIToolbox 0x00007fff90bd0ae3 BlockUntilNextEventMatchingListInMode + 62
18 com.apple.AppKit 0x00007fff94a64533 _DPSNextEvent + 685
19 com.apple.AppKit 0x00007fff94a63df2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
20 com.apple.AppKit 0x00007fff94a5b1a3 -[NSApplication run] + 517
21 com.cycling74.Max 0x0000000100464c1e juce::MessageManager::runDispatchLoop() + 86
22 com.cycling74.Max 0×0000000100338543 juce::JUCEApplication::main(juce::StringArray const&) + 69
23 com.cycling74.Max 0×0000000100338666 juce::JUCEApplication::main(int, char const**) + 68
24 com.cycling74.Max 0x000000010025bb02 main + 637
25 com.cycling74.Max 0×0000000100002332 _start + 224
26 com.cycling74.Max 0×0000000100002251 start + 33


October 23, 2013 | 8:59 am

@roland I see that you’re using Max 6.1.3. You should update to version 6.1.4, which has a fix for your crash.

@roald That’s annoying. I’ve never heard of that button not responding. Do you think you could try to find the crash report manually? You can then send it to support and ask them to forward it to me. Here’s a link for how to find the crash report.

http://bjango.com/help/crashlog/


October 23, 2013 | 8:59 am

@roland I see that you’re using Max 6.1.3. You should update to version 6.1.4, which has a fix for your crash.

@roald That’s annoying. I’ve never heard of that button not responding. Do you think you could try to find the crash report manually? You can then send it to support and ask them to forward it to me. Here’s a link for how to find the crash report.

http://bjango.com/help/crashlog/


October 23, 2013 | 10:27 am

Err….

I am a bit surprised to get a reaction more than three months after my first message.

But OK, I’ve just sent all my Mira crashlogs to you.


October 28, 2013 | 12:23 pm

I’m experiencing Mira crashes every time when I minimize (suspending) an app workflow. Just simply when I click "Home" button on my iPad and then resume to it, Mira kills itself. When opening again, there’s notification "Mira Unexpectedly Quit" with buttons "Send Report" but I think nothing happens when I click on it. I have a crash log from Xcode.


October 28, 2013 | 12:37 pm

@mynde That sounds like a very new and interesting crash. If you can find the crash report file, would you mind sending it to support@cycling74.com? I’ll get right on it.


October 28, 2013 | 1:30 pm

Ok, mail sent.


October 28, 2013 | 10:42 pm

@mynde I hate to be annoying, but if you get the chance could you send the original crash report, rather than the text of the crash report? For some reason, the .rtf file is formatted in a way that makes it basically impossible to understand. I’d really appreciate it.


October 29, 2013 | 2:43 pm

I’ve managed to get original crash report from iPad (plist). Sent mail to support.


Viewing 11 posts - 1 through 11 (of 11 total)