CRASH! CRASH! BAD!

The previous Daslight version

Moderators: TomHat, simonB

schneider007
Posts: 13
Joined: Sat Jan 07, 2017 6:14 pm
Operating System: Mac OS X

CRASH! CRASH! BAD!

Post by schneider007 »

Sorry guys, I've been working with the software a couple of days, planned to use it for a big show, bit I AM DISAPPOINTED! Why are you throwing such a unfixed and unprepared product on the market? Why do you name it "Release candidate"? Is this a joke? It's not funny. I regret that I have purchased the DVC4 GZM!

The pitty is, that the previous version before the 22.12 was more stable, unfortunately you removed the old versions from the website… I didn't test it on Windows, bit on a Mac it's unusable. Try to give the "Dongle" back to the supplier.
beezer
Posts: 7
Joined: Tue Feb 28, 2012 10:26 pm
Operating System: Mac OS X
Location: Germany

Re: CRASH! CRASH! BAD!

Post by beezer »

Here the same! Please FIX IT :cry:
TomHat
Posts: 1371
Joined: Tue Feb 23, 2016 9:11 am
Location: France
Contact:

Re: CRASH! CRASH! BAD!

Post by TomHat »

Hello guys,

Sorry you're experiencing crashes using our software. Have you gotten the chance to notice what triggers these crashes ? Something to help us reproduce and fix them ?

Regards,
TomHat
--
Daslight Support

Mail : [email protected]
Phone (French) : +33 (0) 616 427 588
Phone (English) : +44 (0) 7 481 811 500
schneider007
Posts: 13
Joined: Sat Jan 07, 2017 6:14 pm
Operating System: Mac OS X

Re: CRASH! CRASH! BAD!

Post by schneider007 »

Well, the point is, that this software ist NOT READY (in my opinion) even for a beta status. Lot of things doesn't work as they should. In my opinion the focus should be on a stable, DMX I/O and routing, instead of implementing 20 languages at first…

During the last 2 days I sent a nearly 20 reports (automatically). The crashes on Mac 10.10.2 occur by almost every simple operation, like deleting scenes, groups etc. On the other hand It can't be the way for us users to check your software - WE HAVE TO WORK on our business instead…

I bought the hardware-breakout-controller and the software concerning a new way of arranging a lightshow in a new way, the ideas in your software are excellent, but mainly simple functions, which you find on a 100$ DMX-controller are still missing…

It would take 3 days of collect and report all bugs and deficiencies,… this can't be the task of paying customers.
TomHat
Posts: 1371
Joined: Tue Feb 23, 2016 9:11 am
Location: France
Contact:

Re: CRASH! CRASH! BAD!

Post by TomHat »

Hey,

The crashes on Mac 10.10.2 occur by almost every simple operation, like deleting scenes, groups etc.


Here I'm starting to think that you might not be using the latest version of Daslight 4. Bugs like this have been fixed quite a while ago.

Could you send me your showfile so that I can try to reproduce the crashes on my machine ?

Also, do you have the possibility to test the software on another computer ?

Regards,
TomHat
--
Daslight Support

Mail : [email protected]
Phone (French) : +33 (0) 616 427 588
Phone (English) : +44 (0) 7 481 811 500
schneider007
Posts: 13
Joined: Sat Jan 07, 2017 6:14 pm
Operating System: Mac OS X

Re: CRASH! CRASH! BAD!

Post by schneider007 »

TomHat wrote:Here I'm starting to think that you might not be using the latest version of Daslight 4. Bugs like this have been fixed quite a while ago.


Well, so where I can download the right version? I have only the possibilities to go:

Website > Support > Download > Daslight 4 Official

Are there any other resources? I'll send you the file.
schneider007
Posts: 13
Joined: Sat Jan 07, 2017 6:14 pm
Operating System: Mac OS X

Re: CRASH! CRASH! BAD!

Post by schneider007 »

Some strange things happened:

1. I removed the previous version 22.12 from the Mac (Maintenance Tool)
2. I installed it again 22.12
3. I tried to open the old (problematic) file
4. All fixtures, all Scenes were gone!!! So i got an empty file, despite it was saved on an different location as the program…

…so the file is gone, 2 days of work are gone… I can't retrieve it anymore…
schneider007
Posts: 13
Joined: Sat Jan 07, 2017 6:14 pm
Operating System: Mac OS X

Re: CRASH! CRASH! BAD!

Post by schneider007 »

Is it possible: When I created the file (my show) on an older Beta-Version, and modified it with another newer version, so that mentioned crash problems occur (by deleting a group and saving it immediately)? When I generate a completely new filme, with the same fixtures, everything works fine - the crash problem seems for this time gone?
TomHat
Posts: 1371
Joined: Tue Feb 23, 2016 9:11 am
Location: France
Contact:

Re: CRASH! CRASH! BAD!

Post by TomHat »

Hey,

It could be indeed that there was a problem with your showfile and creating/saving it with an old version of Daslight 4 may have caused problems with parts of your show. I could use the old showfile to be able to tell if there was something wrong with it.

Regards,
TomHat
--
Daslight Support

Mail : [email protected]
Phone (French) : +33 (0) 616 427 588
Phone (English) : +44 (0) 7 481 811 500
schneider007
Posts: 13
Joined: Sat Jan 07, 2017 6:14 pm
Operating System: Mac OS X

Re: CRASH! CRASH! BAD!

Post by schneider007 »

After creating the new file, after 8 Groups and about 5-8 Scenes a group it crashes…! (Performing simple operations, like deleting groups, scenes and saving after that). Who ist programming this?
EricssonStudio
Posts: 5
Joined: Sun Jan 01, 2017 12:23 pm

Re: CRASH! CRASH! BAD!

Post by EricssonStudio »

had crashes all the time on a clean win10 install, changed computer to a win7 just because i wanted to use a touchscreen and now it only crashes on midi fiddling. Its run a week 24/7 and changing 10 scenes 3 times a day. Strange.
PeterC
Posts: 3
Joined: Tue Jan 24, 2017 8:44 pm
Operating System: Windows

Re: CRASH! CRASH! BAD!

Post by PeterC »

Last week end I did a small gig with 15 fixtures only using the Daslight the first time after the use of DMXCreator for several years. The user interface and also the effects are really nice. But the stability of the software is far away what we expect!
It crashed many times, especially when you are editing. Doing edit Tilt/Pan with enabled Linear fan from... a crash can be reproduced very reliable. But also during running a show the software becomes so lazy (delay of several second after switching the scenes) that is has to be restarted again. That is really not what we like! If you are interested in the file could be provided.
beezer
Posts: 7
Joined: Tue Feb 28, 2012 10:26 pm
Operating System: Mac OS X
Location: Germany

Re: CRASH! CRASH! BAD!

Post by beezer »

CRASH 1

Process: Daslight4 [1593]
Path: /Applications/DVC4/*/Daslight4.app/Contents/MacOS/Daslight4
Identifier: dsfsdfsdfsd.Daslight4
Version: 16.1222.0.876
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Daslight4 [1593]
User ID: 501

Date/Time: 2017-01-24 22:52:41.078 +0100
OS Version: Mac OS X 10.12.2 (16C67)
Report Version: 12
Anonymous UUID: DDF46C5F-169C-B194-C57B-DA52C5FA1C2E


Time Awake Since Boot: 2000 seconds

System Integrity Protection: enabled

Crashed Thread: 22 QDasTimer Main Thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
abort() called
*** error for object 0x7ff90cb7d6b0: pointer being freed was not allocated
Thread 22 Crashed:: QDasTimer Main Thread
0 libsystem_kernel.dylib 0x00007fffce3ffdd6 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fffce4eb787 pthread_kill + 90
2 libsystem_c.dylib 0x00007fffce365420 abort + 129
3 libsystem_malloc.dylib 0x00007fffce45503f free + 530
4 libQtDasCore.1.dylib 0x000000010d379d4b CFixture::SetDmxLevel(int, unsigned char) + 635
5 dsfsdfsdfsd.Daslight4 0x000000010bc5f149 CDVCShow::calculateDmx() + 6537
6 dsfsdfsdfsd.Daslight4 0x000000010ba06d35 DVC4::processTask() + 245
7 libQtDasCore.1.dylib 0x000000010d380d72 QDasTimer::processTask() + 322
8 libQtDasCore.1.dylib 0x000000010d3811e4 QDasTimer::MainThread::run() + 84
9 org.qt-project.QtCore 0x000000011078ab3a QThreadPrivate::start(void*) + 362
10 libsystem_pthread.dylib 0x00007fffce4e8aab _pthread_body + 180
11 libsystem_pthread.dylib 0x00007fffce4e89f7 _pthread_start + 286
12 libsystem_pthread.dylib 0x00007fffce4e81fd thread_start + 13
beezer
Posts: 7
Joined: Tue Feb 28, 2012 10:26 pm
Operating System: Mac OS X
Location: Germany

Re: CRASH! CRASH! BAD!

Post by beezer »

CRASH 2 with another Macbook Pro but the same Config and Release year

Process: Daslight4 [1100]
Path: /Applications/Daslight4/*/Daslight4.app/Contents/MacOS/Daslight4
Identifier: dsfsdfsdfsd.Daslight4
Version: 16.1222.0.876
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Daslight4 [1100]
User ID: 501

Date/Time: 2017-01-24 22:56:25.727 +0100
OS Version: Mac OS X 10.12.3 (16D32)
Report Version: 12
Anonymous UUID: DE0F0CB3-39BF-FDB5-EAE7-E9E7E7186025


Time Awake Since Boot: 1100 seconds

System Integrity Protection: enabled

Crashed Thread: 26 Qt HTTP thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'
abort() called
terminating with uncaught exception of type NSException
Thread 26 Crashed:: Qt HTTP thread
0 libsystem_kernel.dylib 0x00007fffd053bdd6 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fffd0627787 pthread_kill + 90
2 libsystem_c.dylib 0x00007fffd04a1420 abort + 129
3 libc++abi.dylib 0x00007fffceffe85a abort_message + 266
4 libc++abi.dylib 0x00007fffcf023c4f default_terminate_handler() + 267
5 libobjc.A.dylib 0x00007fffcfb2db8e _objc_terminate() + 103
6 libc++abi.dylib 0x00007fffcf020d69 std::__terminate(void (*)()) + 8
7 libc++abi.dylib 0x00007fffcf0207de __cxa_throw + 121
8 libobjc.A.dylib 0x00007fffcfb2bb53 objc_exception_throw + 345
9 com.apple.CoreFoundation 0x00007fffbadb596d -[__NSArrayM insertObject:atIndex:] + 1389
10 org.qt-project.QtNetwork 0x000000010e6289b7 QSslSocketBackendPrivate::verifyPeerTrust() + 1927
11 org.qt-project.QtNetwork 0x000000010e624d20 QSslSocketBackendPrivate::startHandshake() + 752
12 org.qt-project.QtNetwork 0x000000010e624e77 QSslSocketBackendPrivate::transmit() + 87
13 org.qt-project.QtCore 0x000000010e051923 QMetaObject::activate(QObject*, int, int, void**) + 883
14 org.qt-project.QtNetwork 0x000000010e5f50fb QAbstractSocketPrivate::canReadNotification() + 235
15 org.qt-project.QtNetwork 0x000000010e601daa QReadNotifier::event(QEvent*) + 42
16 org.qt-project.QtWidgets 0x000000010d1c3edd QApplicationPrivate::notify_helper(QObject*, QEvent*) + 269
17 org.qt-project.QtWidgets 0x000000010d1c6822 QApplication::notify(QObject*, QEvent*) + 5906
18 dsfsdfsdfsd.Daslight4 0x0000000108fa9dd3 DVC4::notify(QObject*, QEvent*) + 67
19 org.qt-project.QtCore 0x000000010e020aa4 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 164
20 org.qt-project.QtCore 0x000000010e072b7a QEventDispatcherUNIXPrivate::activateSocketNotifiers() + 250
21 org.qt-project.QtCore 0x000000010e0735fe QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 1166
22 org.qt-project.QtCore 0x000000010e01ceb1 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401
23 org.qt-project.QtCore 0x000000010de611ae QThread::exec() + 110
24 org.qt-project.QtCore 0x000000010de64b3a QThreadPrivate::start(void*) + 362
25 libsystem_pthread.dylib 0x00007fffd0624aab _pthread_body + 180
26 libsystem_pthread.dylib 0x00007fffd06249f7 _pthread_start + 286
27 libsystem_pthread.dylib 0x00007fffd06241fd thread_start + 13
PeterC
Posts: 3
Joined: Tue Jan 24, 2017 8:44 pm
Operating System: Windows

Re: CRASH! CRASH! BAD!

Post by PeterC »

Here also some more details of the crash from yesterday:

Version=1
EventType=APPCRASH
EventTime=131297666341139459
ReportType=2
Consent=1
UploadTime=131297666344080304
ReportIdentifier=678fda3a-e27b-11e6-8053-e14f4e238a57
IntegratorReportIdentifier=3da01f09-dede-4bf5-9577-ed9910f1f2d3
WOW64=1
NsAppName=Daslight4.exe
AppSessionGuid=00000d88-0002-0016-0f11-be6b8176d201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!Daslight4.exe
TargetAppVer=2016//12//22:15:33:39!0!Daslight4.exe
BootId=4294967295
Response.BucketId=eaff8b6c9dbb7d6f611b4628a026b49f
Response.BucketTable=1
Response.LegacyBucketId=108648244070
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=Daslight4.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=16.1222.7676.1123
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=585bf253
Sig[3].Name=Fehlermodulname
Sig[3].Value=StackHash_dbef
Sig[4].Name=Fehlermodulversion
Sig[4].Value=10.0.14393.479
Sig[5].Name=Fehlermodulzeitstempel
Sig[5].Value=58256ca0
Sig[6].Name=Ausnahmecode
Sig[6].Value=c0000374
Sig[7].Name=Ausnahmeoffset
Sig[7].Value=PCH_06_FROM_ntdll+0x0006EB8C
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=10.0.14393.2.0.0.768.101
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=2055
DynamicSig[22].Name=Zusatzinformation 1
DynamicSig[22].Value=dbef
DynamicSig[23].Name=Zusatzinformation 2
DynamicSig[23].Value=dbef1e687e532f8ddeb1ff541fd77cca
DynamicSig[24].Name=Zusatzinformation 3
DynamicSig[24].Value=4d88
DynamicSig[25].Name=Zusatzinformation 4
DynamicSig[25].Value=4d882e5075e545eae3c29cd1226924c3
UI[2]=C:\Daslight4\Daslight4\Daslight4.exe
UI[3]=Computerized Lighting Controller funktioniert nicht mehr
UI[4]=Windows kann online nach einer Lösung für das Problem suchen.
UI[5]=Online nach einer Lösung suchen und das Programm schließen
UI[6]=Später online nach einer Lösung suchen und das Programm schließen
UI[7]=Programm schließen
LoadedModule[0]=C:\Daslight4\Daslight4\Daslight4.exe
....
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Nicht mehr funktionsfähig
ConsentKey=APPCRASH
AppName=Computerized Lighting Controller
AppPath=C:\Daslight4\Daslight4\Daslight4.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=628AAE1136B5C15A6C9D18393E69053B
MetadataHash=-526239058
Post Reply