Crashes when I start adding changing the video in a placer

Since this appears to be the only means of support, I am begging for help at this point… Anyone else have this issue? Anyone see what to fix?

I am quite upset with the tool right now, and without a support line I am not believing this tool is ready for production.

But… the problem, in a nut shell, is in the subject. I add a series of media objects, put them in a placer with multiple items, and it craps out completely to desktop.

Dump from the console:

Process: BoinxTV [15234]
Path: /Applications/BoinxTV.localized/
Identifier: com.boinx.BoinxTV.Full
Version: 1.9.7 (17041)
App Item ID: 414473844
App External ID: 457292656
Code Type: X86 (Native)
Parent Process: launchd [263]
Responsible: BoinxTV [15234]
User ID: 503

Date/Time: 2014-06-10 12:38:11.309 -0400
OS Version: Mac OS X 10.9.3 (13D65)
Report Version: 11
Anonymous UUID: 7405FECE-EDA3-AAF3-3FC6-03EE5D37E8C4

Crashed Thread: 28 BoinxTV:0x10290bb0:OutputRenderingThread Dispatch queue:

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000ffffffff

VM Regions Near 0xffffffff:
–> shared memory 00000000ffff8000-00000000ffff9000 [ 4K] r-x/r-x SM=SHM

Thread 0:: Dispatch queue:
0 0x9b18740e -[NSWindow _backingType] + 15
1 0x9b1873ed -[NSWindow _allowsCompositing] + 59
2 0x9b187ccc -[NSWindow _threadContextForCompositing:] + 44
3 0x9b187c9b -[NSWindow _threadContext] + 41
4 0x9b19d8d4 -[NSView _contextForLockFocus:] + 130
5 0x9b1d240b -[NSView unlockFocus] + 180
6 0x9b1a02af -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 5415
7 0x9b1a00b6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4910
8 0x9b1a00b6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4910
9 0x9b1a00b6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 4910
10 0x9b19e8f0 -

etc etc…

“Since this appears to be the only means of support,” you know our support staff is waiting at or for your request?

To your crash: It stops where it gets interesting. Can you please send the entire crash log to our support staff via email and ask them to hand it to me, also mentioning the link to this forum thread :

That log, and one where I was just switching between videos in a feed have been sent. If you need any other information, please let me know. I must have this rock-solid for our July Webinar.

Looking at the log, BoinxTV ran out of memory. Currently BoinxTV is 32-Bit, that means it is limited to 4GB of RAM. The log also shows that your document holds a lot of videos. each video needs to be loaded to RAM on launch. If you can, remove all videos you don’t need from the document.
We currently work on a 64 Bit BoinxTV 2 version that will eliminate the Memory issue, it’s just not an easy task :frowning:

Ugh, maybe a short term solution is to put an error message or something up… crashing hurt bad.

So, is the limit purely file size? If I optimize the video (all compresses down to a single mp4 less than 500Meg), will that absolutely avoid the crashes?