Daslight Forum

Dear Support Team,

I am experiencing issues with Daslight 5 and would appreciate your assistance.

## Issue Description
- Application crashes when trying to open Daslight 4 project files in Daslight 5
- While the file opens initially, it crashes whenever I try to operate it
- Current file size is 75MB
- I confirmed that small files (1.8MB) work properly
- However, for our actual operation, we need files larger than 100MB
- In Daslight 4, we could work with files over 300MB without any issues

## Environment
- OS: macOS 14.3.1 (23D60)
- Daslight 5 Version: 24.1205.158.90
- Application Type: x86-64 (Native)

## Error Details
- Error Type: EXC_CRASH (SIGABRT)
- Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
- Memory allocation failure (vm_allocate_kernel failed) is reported

## Steps Taken
- Restarted the application
- Restarted the computer
- Tested with small file (1.8MB) which worked successfully

Could you please advise on possible solutions to handle large project files without crashes?
Your assistance would be greatly appreciated.

Hello,

Thanks for raising this thread! Could you please send over the .dvc file that causes this crash to occur so that we can test it ourselves? You may need to use a file sharing service to do this if the file size is too large.

Kind regards,
Will

Hello Will,

Thank you for your quick response. I have uploaded the .dvc file that causes the crash:

https://we.tl/t-qkBF3prG7Z

The file is available for download for 7 days. Please let me know if you need any additional information.

Best regards,
Yuuji

Hello Will,

The previous file link has expired, so I have uploaded a new one:
https://we.tl/t-uvCL9l0uRz

I would like to provide additional information about our system environment:

Our MacBook Pro is equipped with a 2 GHz Quad-Core Intel Core i5, which meets the minimum requirements for Daslight 5, but falls short of the recommended Core i7 specification.

In the future, we plan to use a MIDI controller for simultaneous control of video, audio, and lighting. We are concerned about system resources, as we are already experiencing errors with Daslight 5 alone.

While we have purchased the Daslight 5 interface, we have not yet connected it to any lighting equipment via DMX cable. These errors are occurring during the initial application testing phase.

We are under tight project deadlines and would greatly appreciate a timely resolution. Please let me know if you need any additional information to assist with troubleshooting.

Best regards

Dear Daslight Community,

I am writing to seek your expertise regarding an issue I'm experiencing with Daslight 5, where the CPU usage becomes excessively high.

Recently, I've observed the following:

* **CPU Usage Spikes to 700% Upon File Opening:**

As soon as I launch Daslight 5 and open a project file, the CPU usage immediately surges to over 700%. This occurs even when no operations are being performed within the application.

My system environment is as follows:

* MacBook Pro (13-inch, 2020)
* Processor: 2 GHz Quad-Core Intel Core i5
* Graphics: Intel Iris Plus Graphics
* Memory: 16 GB
* Operating System: macOS Sequoia 15.2

Attached are screenshots from Activity Monitor , showcasing the CPU and memory usage by Daslight 5.

I believe the problem might stem from one of the following factors:

* **Hardware Limitations:**

Is it possible that the Intel Core i5 processor and integrated Intel Iris Plus Graphics are insufficient for Daslight 5 to operate smoothly?

* **File Format Compatibility:**

Could the use of project files originally created in Daslight 4 contribute to the high CPU usage in Daslight 5?

* **Software Glitches:**

Is it possible that there are underlying software issues within Daslight 5 that are causing this behavior?

I would appreciate your insights on the following questions:

1. Are there any users in the community who have successfully used Daslight 5 on a similar configuration (Core i5 & Integrated Graphics)? If so, what has been your experience?

2. Have you encountered any instances where file format conversions (Daslight 4 to Daslight 5) have resulted in excessive CPU usage?

3. Are there any alternative causes or potential solutions that I may have overlooked?

Any guidance or suggestions you can provide would be greatly appreciated. Please do not hesitate to request any additional information that may be helpful in troubleshooting this issue.

Thank you in advance for your time and assistance.

Best regards,
Yuuji

Dear Daslight Community,

I have identified a new and crucial piece of information.

Please consider the following:

Crash Reproduction: The issue reliably occurs when attempting to open an 8.8MB Daslight 5 project file. This file is being shared with the community for the first time.
Operation at Crash: After launching Daslight 5, I click the "Open" button, select the file, and click the "Open" button to confirm. The crash reliably occurs at this point, before the file loading process can fully complete.
CPU Usage Profile: I have recorded a video demonstrating the crash.
Around the 21-second mark: Immediately after clicking the "Open" button, the CPU usage rapidly spikes to over 600%.
Around the 33-second mark: CPU load stabilizes back to approximately 118%.
Around the 1 minute and 7-second mark: Daslight 5 then abruptly terminates.
Previously, the application crashed during active use with the CPU locked at high usage ( 700% ). This new test shows the CPU briefly stabilizes at 118% before the crash, which indicates a potentially different cause of the crash.
System Specifications:
MacBook Pro (13-inch, 2020)
Processor: 2 GHz Quad-Core Intel Core i5
Graphics: Intel Iris Plus Graphics
Memory: 16 GB
Operating System: macOS Sequoia 15.2

I've also attached the crash report: the following key info:
Crashed Thread: 48 Thread (pooled)
Thread 48 Crashed:: Thread (pooled)
0 libsystem_kernel.dylib 0x7ff80d347c52 __pthread_kill + 10
1 libsystem_pthread.dylib 0x7ff80d381f85 pthread_kill + 262
2 libsystem_c.dylib 0x7ff80d2a2b19 abort + 126
3 libc++abi.dylib 0x7ff80d339163 abort_message + 258
4 libc++abi.dylib 0x7ff80d32a0b4 demangling_terminate_handler() + 240
5 libobjc.A.dylib 0x7ff80cfc6d69 _objc_terminate() + 104
6 libc++abi.dylib 0x7ff80d33853b std::__terminate(void (*)()) + 6
7 libc++abi.dylib 0x7ff80d3384f6 std::terminate() + 54
8 QtCore 0x1105ef77c 0x1105cd000 + 141180
9 libsystem_pthread.dylib 0x7ff80d382253 _pthread_start + 99
10 libsystem_pthread.dylib 0x7ff80d37dbef thread_start + 15

Currently, I'm unsure of the answers to these questions:

What specific tasks are being handled by Thread 48 at the moment of the crash?
What is leading Daslight 5 to call "Abort()", since the high CPU usage is resolving before the crash?
What factors are leading to such high initial CPU usage, even though the file is relatively small at 8.8MB?

I would appreciate your guidance:

Are there any users in the community who have successfully used Daslight 5 on a similar configuration (Core i5 & Integrated Graphics)? Has anyone experienced crashes during file loading, specifically?
Would anyone be willing to test the attached 8.8MB project file to see if it causes a similar crash on your system?
Based on the crash report, attached video, and previous descriptions, what potential causes or solutions can you suggest?

attachment
Crash Recording Video
https://we.tl/r-bPfNnKztGv
Error Report
https://we.tl/t-Ffcj64PoXX
project file
https://we.tl/t-hyXLBTpiiR

Thank you in advance for your time and expertise,

Yuuji