mattyo

I just changed the aspect ratios of a video mixer patch I've been working on and using for some time. It has been rock-solid, but since that change (and I haven't really touched anything else), it's become very unstable when using a camera, including the Macbook built in one.

From my very limited understanding of crash logs, I think something is going pear-shaped when the offcreen buffer is swapped in (maybe), and I thought having a handle on what was leading up to it might help me troubleshoot.

If anyone can have a glance & help me out, I'd appreciate it.....

PS: Can't upload crashlogs, I see "for security reasons". OK, here's the relevant thread:

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

0 libsystem_kernel.dylib     0x97fe969a __pthread_kill + 10

1 libsystem_pthread.dylib     0x98211f19 pthread_kill + 101

2 libsystem_c.dylib     0x95d5feee abort + 156

3 libGPUSupportMercury.dylib     0x920de942 gpusGenerateCrashLog + 187

4 com.apple.GeForceGLDriver     0x48254632 0x48000000 + 2442802

5 libGPUSupportMercury.dylib     0x920dff46 gpusSubmitDataBuffers + 533

6 com.apple.GeForceGLDriver     0x4835a572 0x48000000 + 3515762

7 com.apple.GeForceGLDriver     0x4835a9c7 gldPresentFramebufferData + 230

8 GLEngine     0x900e10ce glSwap_Exec + 110

9 com.apple.opengl     0x926d832f CGLFlushDrawable + 67

10 com.apple.AppKit     0x9864a0e6 -[NSOpenGLContext flushBuffer] + 25

11 com.cycling74.JitterAPI     0x12904dc6 nsglSwapBuffers + 33

12 com.cycling74.JitterAPI     0x128418d4 jit_gl_context_swap_buffers + 39

13 com.cycling74.JitterAPI     0x128e5194 jit_gl_context_view_swap + 94

14 com.cycling74.Max     0x00170e85 object_method_imp + 326

15 com.cycling74.JitterAPI     0x1285ceed jit_object_method + 149

16 com.cycling74.jit-gl-render     0x1955a4fc jit_gl_render_drawswap + 126

17 com.cycling74.Max     0x00170e85 object_method_imp + 326

18 com.cycling74.JitterAPI     0x1285ceed jit_object_method + 149

19 com.cycling74.JitterAPI     0x128784ec max_jit_defer_method_doit + 69

20 com.cycling74.JitterAPI     0x12878568 max_jit_defer_low_method + 118

21 com.cycling74.Max     0x0009aecb typedmess_fun + 295

22 com.cycling74.Max     0x0009ab29 typedmess + 72

23 com.cycling74.jit-gl-render     0x1955b69b max_jit_gl_render_bang + 52

24 com.cycling74.Max     0x0010d2a9 outlet_bang + 1045

25 com.cycling74.Max     0x000f4491 trigger_iterate + 144

26 com.cycling74.Max     0x000f4301 trigger_bang + 87

27 com.cycling74.Max     0x0010d2a9 outlet_bang + 1045

28 com.cycling74.metro     0x127ada4d metro_out + 99

29 com.cycling74.Max     0x000ac932 sched_dequeue + 274

30 com.cycling74.Max     0x0030558c MainThreadEventHandler::invoke() + 106

31 com.cycling74.Max     0x003057db non-virtual thunk to MainThreadEventHandler::timerCallback() + 27

32 com.cycling74.Max     0x0044de00 juce::InternalTimerThread::callTimers() + 148

33 com.cycling74.Max     0x0044dccc non-virtual thunk to juce::InternalTimerThread::handleMessage(juce::Message const&) + 20

34 com.cycling74.Max     0x0044cce9 juce::MessageManager::deliverMessage(juce::Message*) + 61

35 com.cycling74.Max     0x0053c723 juce::AppDelegateRedirector::runLoopCallback() + 113

36 com.apple.CoreFoundation     0x922cd12f __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15

37 com.apple.CoreFoundation     0x922bec8e __CFRunLoopDoSources0 + 462

38 com.apple.CoreFoundation     0x922be0f2 __CFRunLoopRun + 994

39 com.apple.CoreFoundation     0x922bdaa6 CFRunLoopRunSpecific + 390

40 com.apple.CoreFoundation     0x922bd90b CFRunLoopRunInMode + 123

41 com.apple.HIToolbox     0x93de68f8 RunCurrentEventLoopInMode + 262

42 com.apple.HIToolbox     0x93de6503 ReceiveNextEventCommon + 192

43 com.apple.HIToolbox     0x93de642c _BlockUntilNextEventMatchingListInModeWithFilter + 99

44 com.apple.AppKit     0x98387721 _DPSNextEvent + 742

45 com.apple.AppKit     0x98386dc5 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 350

46 com.apple.AppKit     0x9837b77c -[NSApplication run] + 907

47 com.cycling74.Max     0x003e3ff9 -[MaxCefApplication run] + 58

48 com.cycling74.chromium     0x00e37c6e 0xd0b000 + 1231982

I just changed the aspect ratios of a video mixer patch I've been working on and using for some time.  It has been rock-solid, but since that change (and I haven't really touched anything else), it's become very unstable when using a camera, including the Macbook built in one.

From my very limited understanding of crash logs, I think something is going pear-shaped when the offcreen buffer is swapped in (maybe), and I thought having a handle on what was leading up to it might help me troubleshoot.  

PS: Can't upload crashlogs, I see "for security reasons".  OK, here's the relevant thread:

Thread 0 Crashed:: CrBrowserMain  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x97fe969a __pthread_kill + 10
1   libsystem_pthread.dylib       	0x98211f19 pthread_kill + 101
2   libsystem_c.dylib             	0x95d5feee abort + 156
3   libGPUSupportMercury.dylib    	0x920de942 gpusGenerateCrashLog + 187
4   com.apple.GeForceGLDriver     	0x48254632 0x48000000 + 2442802
5   libGPUSupportMercury.dylib    	0x920dff46 gpusSubmitDataBuffers + 533
6   com.apple.GeForceGLDriver     	0x4835a572 0x48000000 + 3515762
7   com.apple.GeForceGLDriver     	0x4835a9c7 gldPresentFramebufferData + 230
8   GLEngine                      	0x900e10ce glSwap_Exec + 110
9   com.apple.opengl              	0x926d832f CGLFlushDrawable + 67
10  com.apple.AppKit              	0x9864a0e6 -[NSOpenGLContext flushBuffer] + 25
11  com.cycling74.JitterAPI       	0x12904dc6 nsglSwapBuffers + 33
12  com.cycling74.JitterAPI       	0x128418d4 jit_gl_context_swap_buffers + 39
13  com.cycling74.JitterAPI       	0x128e5194 jit_gl_context_view_swap + 94
14  com.cycling74.Max             	0x00170e85 object_method_imp + 326
15  com.cycling74.JitterAPI       	0x1285ceed jit_object_method + 149
16  com.cycling74.jit-gl-render   	0x1955a4fc jit_gl_render_drawswap + 126
17  com.cycling74.Max             	0x00170e85 object_method_imp + 326
18  com.cycling74.JitterAPI       	0x1285ceed jit_object_method + 149
19  com.cycling74.JitterAPI       	0x128784ec max_jit_defer_method_doit + 69
20  com.cycling74.JitterAPI       	0x12878568 max_jit_defer_low_method + 118
21  com.cycling74.Max             	0x0009aecb typedmess_fun + 295
22  com.cycling74.Max             	0x0009ab29 typedmess + 72
23  com.cycling74.jit-gl-render   	0x1955b69b max_jit_gl_render_bang + 52
24  com.cycling74.Max             	0x0010d2a9 outlet_bang + 1045
25  com.cycling74.Max             	0x000f4491 trigger_iterate + 144
26  com.cycling74.Max             	0x000f4301 trigger_bang + 87
27  com.cycling74.Max             	0x0010d2a9 outlet_bang + 1045
28  com.cycling74.metro           	0x127ada4d metro_out + 99
29  com.cycling74.Max             	0x000ac932 sched_dequeue + 274
30  com.cycling74.Max             	0x0030558c MainThreadEventHandler::invoke() + 106
31  com.cycling74.Max             	0x003057db non-virtual thunk to MainThreadEventHandler::timerCallback() + 27
32  com.cycling74.Max             	0x0044de00 juce::InternalTimerThread::callTimers() + 148
33  com.cycling74.Max             	0x0044dccc non-virtual thunk to juce::InternalTimerThread::handleMessage(juce::Message const&) + 20
34  com.cycling74.Max             	0x0044cce9 juce::MessageManager::deliverMessage(juce::Message*) + 61
35  com.cycling74.Max             	0x0053c723 juce::AppDelegateRedirector::runLoopCallback() + 113
36  com.apple.CoreFoundation      	0x922cd12f __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
37  com.apple.CoreFoundation      	0x922bec8e __CFRunLoopDoSources0 + 462
38  com.apple.CoreFoundation      	0x922be0f2 __CFRunLoopRun + 994
39  com.apple.CoreFoundation      	0x922bdaa6 CFRunLoopRunSpecific + 390
40  com.apple.CoreFoundation      	0x922bd90b CFRunLoopRunInMode + 123
41  com.apple.HIToolbox           	0x93de68f8 RunCurrentEventLoopInMode + 262
42  com.apple.HIToolbox           	0x93de6503 ReceiveNextEventCommon + 192
43  com.apple.HIToolbox           	0x93de642c _BlockUntilNextEventMatchingListInModeWithFilter + 99
44  com.apple.AppKit              	0x98387721 _DPSNextEvent + 742
45  com.apple.AppKit              	0x98386dc5 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 350
46  com.apple.AppKit              	0x9837b77c -[NSApplication run] + 907
47  com.cycling74.Max             	0x003e3ff9 -[MaxCefApplication run] + 58
48  com.cycling74.chromium        	0x00e37c6e 0xd0b000 + 1231982
49  com.cycling74.chromium        	0x00e3754c 0xd0b000 + 1230156
50  com.cycling74.chromium        	0x00e7afd2 0xd0b000 + 1507282
51  com.cycling74.chromium        	0x00e95c7e 0xd0b000 + 1617022
52  com.cycling74.chromium        	0x00e7a9ba 0xd0b000 + 1505722
53  com.cycling74.chromium        	0x00d83ade 0xd0b000 + 494302
54  com.cycling74.Max             	0x003e4007 -[MaxCefApplication run] + 72
55  com.cycling74.Max             	0x00537237 juce::MessageManager::runDispatchLoop() + 589
56  com.cycling74.Max             	0x003f9ad4 juce::JUCEApplication::main(juce::StringArray const&) + 62
57  com.cycling74.Max             	0x003f9be9 juce::JUCEApplication::main(int, char const**) + 73
58  com.cycling74.Max             	0x0006dd15 start + 53


hoping-for-some-crash-report-interpretation

you should use pastebin and paste the whole crashlog

you should use pastebin and paste the whole crashlog
or uploade it her eas a txt
Did you install an external patch ?


The whole crashlog was not accepted. "Sorry, this file type is not permitted for security reasons." OK, I was lazy. Here it is as a textfile:

The whole crashlog was not accepted.  "Sorry, this file type is not permitted for security reasons."  OK, I was lazy.  Here it is as a textfile:


hi mattyo. if you can isolate this problem into a simple patch with some steps to reproduce, we'd be happy to take a look and try and track down the problem.

Hi Rob -- I was hoping to have a clue from the crashlogs as to what direction to start looking in, as the patch is rather a beast. Well, I'll start pulling it apart....

Hi Rob -- I was hoping to have a clue from the crashlogs as to what direction to start looking in, as the patch is rather a beast.  Well, I'll start pulling it apart....

Hoping for some crash report interpretation