Visual Productions forum

Author Topic: Crashes When Deleting Cue Targets  (Read 5553 times)

March 25, 2010, 12:18:14 AM
Read 5553 times

KnowSlumber

  • Member
  • *
  • Posts: 145
Cuelux is crashng every time I try to remove a target fixture via the cue editor.
This is compounded by the fact that the record button is recording non-selected fixtures as targets in my cues.

So now all my cues have targets fixtures I didn't select, which I can't get rid of.
At a total loss.
Anyone else having this problem?

This is really really bad.
« Last Edit: March 25, 2010, 12:25:19 AM by KnowSlumber »

March 25, 2010, 12:34:44 AM
Reply #1

vnx

  • Member
  • *
  • Posts: 93
Hi,

I also experienced several crashes while deleting targets and other things I did in the programmer, but never any problems with the record button. The programmer is definitely something to have a sharp look on in terms of crashes.

BTW: Don't expect Maarten or Jeroen to answer in short time. As Maarten told in another thread they are on a trade show in Frankfurt/Germany. I guess that took a pretty good amount of time for preparation and that's why they were not that involved in to forum the last days. I am confident that they are back online next week to answer all of our burning questions ;-)

Best,

Ben
« Last Edit: March 25, 2010, 12:47:56 AM by vnx »
Cuelux 1.03b22 on MacBook Pro (MacOSX 10.6.5) / Thinkpad X41t (WinXP) using Livid Ohm64 Controller

March 25, 2010, 12:58:15 AM
Reply #2

KnowSlumber

  • Member
  • *
  • Posts: 145
Gotcha.

I should add that the crashes corrupt the saved show files and make them unusable.

March 25, 2010, 08:03:17 AM
Reply #3

popy

  • Guest
I also have several crashes inside the programmer.

But my show file is intact

cu
pOpY

March 26, 2010, 06:57:37 AM
Reply #4

markbrown

  • Member
  • *
  • Posts: 5
Same problem here, no corrupted save files yet, but I did have a crash from trying to remove a fixture from a cue that wiped out everything I had done.

I also get crashes when trying to edit cues when using the wizard.

March 28, 2010, 04:18:21 PM
Reply #5

vnx

  • Member
  • *
  • Posts: 93
Hi,

To the people that got corrupt show files: in what way they were corrupted, were they just empty or wrong data in it?
Generally, I think that it would be great to have one or two backups of the show files automatically generated on auto-safe. So when Cuelux crashes and leaves some chaos behind, there is still a backup to revert to.

Best,

Ben
Cuelux 1.03b22 on MacBook Pro (MacOSX 10.6.5) / Thinkpad X41t (WinXP) using Livid Ohm64 Controller

March 29, 2010, 08:18:13 PM
Reply #6

Maarten Engels

  • Administrator
  • Member
  • *****
  • Posts: 2383
    • www.visualproductions.nl
We haven't come across any situation that corrupts the show file, but... If you ever get to the point you have show.xml that is corrupted in a way it doesn't load any more or creates other sorts of problems then please send it to us, we would learn a great deal from such a file.

Generally, I think that it would be great to have one or two backups of the show files automatically generated on auto-safe. So when Cuelux crashes and leaves some chaos behind, there is still a backup to revert to.
This sounds like a good idea to implement. We could go for an hourly backup in a special folder. Or can we think of a different approach?
Maarten Engels
Visual Productions BV

March 30, 2010, 05:14:33 PM
Reply #7

vnx

  • Member
  • *
  • Posts: 93
Hi Maarten,

An hourly backup does not help, when you are in the middle of a programming session and things tend to change very fast. I think the more reasonable approach would be to keep at least two generations of the auto-safed show file. I believe that the show files only gets corrupted when Cuelux has crashed while auto-saving so there is little chance that these backups get corrupted as well, when you backup the last working file before the actual auto-saving happens. Maybe there is even a way to detect when things had gone wrong, e.g. the show file is empty or the XML is not well-formed or does not validate against it's DTD or XML Schema anymore. Cuelux could then also warn if it tries to auto-safe potentially corrupted data. Same goes for restarting Cuelux after a crash: it could then offer some kind of crash recovery by offering to open one of the backups. While in the process of recovering the last working state Cuelux should by no means continue auto-saving because potential important backups could get overwritten. Auto-Safe could be resumed when the user has found a working backup and manually safed it to disk.

Just a few ideas. There are actually many ways to make Cuelux more safe against the results of a severe crash with potential data loss. While also experiencing crashes in recent versions with the programmer (esp. deleting targets) I only had some corrupted (empty) files in the pre 1.x versions. But maybe I was just lucky and Cuelux managed to safe a working show file before it crashed.
While crashing software can be a spoiler more important is that it does never ever loses some data while doing so as this is the real show stopper (in the true sense of the word ;-)).

Best,

Ben
Cuelux 1.03b22 on MacBook Pro (MacOSX 10.6.5) / Thinkpad X41t (WinXP) using Livid Ohm64 Controller

April 01, 2010, 11:12:30 AM
Reply #8

Maarten Engels

  • Administrator
  • Member
  • *****
  • Posts: 2383
    • www.visualproductions.nl
Thanks, this makes good sense to me. I might come back to this subject when I am actually implementing the code and need some more input.
Maarten Engels
Visual Productions BV

April 01, 2010, 04:40:12 PM
Reply #9

Maarten Engels

  • Administrator
  • Member
  • *****
  • Posts: 2383
    • www.visualproductions.nl
Just fixed the bug that caused the crash when deleting Targets from a Cuelist.
Maarten Engels
Visual Productions BV

April 08, 2010, 11:14:39 PM
Reply #10

beezer

  • Member
  • *
  • Posts: 82
  • Macbook / Cuelux / Virtual DJ
Process:         Cuelux [652]
Path:            /Volumes/cuelux1024/Cuelux.app/Contents/MacOS/Cuelux
Identifier:      com.VisualProductions.Cuelux
Version:         Cuelux version 1.02 (1.0)
Code Type:       X86 (Native)
Parent Process:  launchd [466]

Date/Time:       2010-04-08 23:11:31.053 +0200
OS Version:      Mac OS X 10.6.3 (10D573)
Report Version:  6

Interval Since Last Report:          67676 sec
Crashes Since Last Report:           1
Per-App Interval Since Last Report:  894 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      7E4C4E57-665F-4C5B-9DDF-0ADC54351051

Exception Type:  EXC_CRASH (SIGBUS)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread:  1  Dispatch queue: com.apple.libdispatch-manager

Thread 0:  Dispatch queue: com.apple.main-thread
0   com.VisualProductions.Cuelux     0x0002921d CPrxPlayback::SetGroup(CPrxGroup const*) + 57
1   com.VisualProductions.Cuelux     0x0006343c CAreaViewPlay::OnClose(CArea*, TModalResult) + 84
2   com.VisualProductions.Cuelux     0x000ffa56 CArea::Timer(float) + 66
3   com.VisualProductions.Cuelux     0x000ffaa5 CArea::Timer(float) + 145
4   com.VisualProductions.Cuelux     0x000ffaa5 CArea::Timer(float) + 145
5   com.VisualProductions.Cuelux     0x0010f27b CUi::Loop() + 1255
6   com.VisualProductions.Cuelux     0x000af786 SDL_main + 554
7   com.VisualProductions.Cuelux     0x00002ad7 -[SDLMain applicationDidFinishLaunching:] + 66
8   com.apple.Foundation             0x94517274 _nsnote_callback + 345
9   com.apple.CoreFoundation         0x92c7e3f9 __CFXNotificationPost + 905
10  com.apple.CoreFoundation         0x92c7de2a _CFXNotificationPostNotification + 186
11  com.apple.Foundation             0x9450c098 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128
12  com.apple.Foundation             0x94519475 -[NSNotificationCenter postNotificationName:object:] + 56
13  com.apple.AppKit                 0x95b86dba -[NSApplication _postDidFinishNotification] + 125
14  com.apple.AppKit                 0x95b86cca -[NSApplication _sendFinishLaunchingNotification] + 74
15  com.apple.AppKit                 0x95cddd85 -[NSApplication(NSAppleEventHandling) _handleAEOpen:] + 274
16  com.apple.AppKit                 0x95cdd9a5 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 101
17  com.apple.Foundation             0x9454c408 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 511
18  com.apple.Foundation             0x9454c1cc _NSAppleEventManagerGenericHandler + 228
19  com.apple.AE                     0x9814cf58 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 166
20  com.apple.AE                     0x9814ce57 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 43
21  com.apple.AE                     0x9814cd61 aeProcessAppleEvent + 197
22  com.apple.HIToolbox              0x93b91487 AEProcessAppleEvent + 50
23  com.apple.AppKit                 0x95b57372 _DPSNextEvent + 1420
24  com.apple.AppKit                 0x95b56976 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
25  com.apple.AppKit                 0x95b18bef -[NSApplication run] + 821
26  com.VisualProductions.Cuelux     0x0000323a main + 1567
27  com.VisualProductions.Cuelux     0x00002292 _start + 216
28  com.VisualProductions.Cuelux     0x000021b9 start + 41


April 09, 2010, 09:09:31 AM
Reply #11

Maarten Engels

  • Administrator
  • Member
  • *****
  • Posts: 2383
    • www.visualproductions.nl
@ beezer

Thanks for the info, can you describe what you were doing leading up to the crash? Then I can try to reproduce the error.
Maarten Engels
Visual Productions BV

April 09, 2010, 11:00:55 PM
Reply #12

markbrown

  • Member
  • *
  • Posts: 5
Just fixed the bug that caused the crash when deleting Targets from a Cuelist.

Excellent news!
any word on when the updated version of the software with this bug fix will be released?

 

SMF spam blocked by CleanTalk