Crash on OSX 10.9.1 when used with splitted *.RAW, *.R01 files

[tecgen]

Hi Andrew,

thank you for your great viewer. Such an application helps a lot to preview our clips.

I noticed that the application crash when I started it on a .RAW file which also has a splitted .R01 file with the same name. I used a 50d in crop mode to record a clip in 1920x1080px resolution.

Let me know I you need more informations or when I should confirm a bugfix.

Best regards, Marco

[Andrew Baldwin]

I'm not able to reproduce this. For me it is working ok with spanning/splitted RAW/R01/R02.. files and spanning MLV/ML0 files.

I tried to make a similar resolution / crop set, but no luck.

Can you try to run the app from the command line to give possibly more information about the crash? http://www.magiclantern.fm/forum/index.php?topic=9560.msg92162#msg92162

[tecgen]

Hi Andrew,

since I delete my old RAW files, I needed to record a new spanned clip. That means I can still reproduce the bug. Here is my command line output.

MlRawViewer v1.0.1
(c) Andrew Baldwin & contributors 2013
Opening MLRAW file /Volumes/SSD2/RAW Shoots/RAW/M20-2154.RAW
Black level: 1787
2013-12-20 22:03:16.909 mlrawviewer[456:507] NSDocumentController Info.plist warning: The values of CFBundleTypeRole entries must be 'Editor', 'Viewer', 'None', or 'Shell'.
2013-12-20 22:03:16.910 mlrawviewer[456:507] NSDocumentController Info.plist warning: The values of CFBundleTypeRole entries must be 'Editor', 'Viewer', 'None', or 'Shell'.
Width: 1920 Height: 1080 Frames: 1287
Using Bilinear demosaic algorithm
Segmentation fault: 11

Stacetrace from the OSX report:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_platform.dylib        0x00007fff880520de _platform_memmove$VARIANT$Nehalem + 254
1   libGLImage.dylib                0x00007fff8e099f93 glgCopyRowsWithMemCopy(GLGOperationRec const*, unsigned long, GLDPixelModeRec const*) + 61
2   libGLImage.dylib                0x00007fff8e098c56 glgProcessPixelsWithProcessor + 1392
3   com.apple.AMDRadeonX3000GLDriver    0x00001234801e79a6 0x123480000000 + 1997222
4   com.apple.AMDRadeonX3000GLDriver    0x000012348021cb78 0x123480000000 + 2214776
5   GLEngine                        0x00007fff8bb238a9 glTexSubImage2D_Exec + 1169
6   libGL.dylib                     0x00007fff926968d4 glTexSubImage2D + 75
7   libffi.dylib                    0x00007fff9303ef9c ffi_call_unix64 + 76
8   libffi.dylib                    0x00007fff9303f78e ffi_call + 790
9   _ctypes.so                      0x000000010fd4b90e _ctypes_callproc + 794
10  _ctypes.so                      0x000000010fd45f80 0x10fd43000 + 12160
11  Python                          0x000000010f59af72 PyObject_Call + 101
12  Python                          0x000000010f615395 PyEval_EvalFrameEx + 16856
13  Python                          0x000000010f611093 PyEval_EvalCodeEx + 1641
14  Python                          0x000000010f5b8796 0x10f591000 + 161686
[..]

I am running the application following notebook. The OS switch to the discrete graphics card when I start the application.

Model: MacBookPro8,3, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.2 GHz, 16 GB, SMC 1.70f6
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 1024 MB

Best regards, Marco

[Andrew Baldwin]

Very useful info. Thanks for collecting this. Just one more question:

Does the crash occur as soon as the split RAW file is opened, or only after the first file has played through and it starts to display the second?

Do you see any frames of the set drawn correctly to the screen?

[tecgen]

I can view the first .RAW file, but when the second .R00 is supposed to be shown automatically the application crashed. I can not remember that it happen when I used MLV files, when I tried the newer mlv_rec module some days ago.

By the way, when I force my Macbook to use the integrated Intel HD 3000 graphics instead of the ATI Radeon I can reproduce the same behavior. It seams to me that it has nothing to do with the type of graphics card.

[tecgen]

I just want you to know. I tried version 1.0.3 alpha and can reproduce the bug.

[Andrew Baldwin]

Is this still reproducible in 1.1.3?