olive-editor/olive

[CRASH] Olive completely shuts down (crashes) computer during export of 5 min video on Windows 10

rempsyc opened this issue · 2 comments

Commit Hash

Olive version 0.2.0-1687a721

Platform

Type: Laptop ASUS K55A
OS: Windows 10 Version 10.0.19045 Build 19045
Processor: Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz 2.40 GHz
Installed RAM: 16.0 GB (15.5 GB usable)
Graphics Card: Intel(R) HD Graphics 4000

Summary

I am experiencing a reliable crash when exporting a 5:21:56 (5 min) long video with default export options that combines 6 videos of total size 293 MB (no modifications or special effects). To be clear it is not Olive that is crashing, but Olive that is making my whole computer shut down toward the end of the export, which then has to be rebooted manually.

Seems like processor is maxed out before the RAM in this process. Are my specs too low to export a 5 min video in Olive?

Possibly linked to #2153?

Steps to Reproduce

  1. Drag and drop videos in a project sequence to be about 5 min long
  2. Ctrl+M and export with default options
  3. Wait until the end, and experience a PC shut down
Crash Report


I am not able to find a crash report, because my PC is forced shut down along with Olive, which prevents my access to any crash report (I think? It does not appear in the same folder as the Olive file/video and could not find a crash report folder in C:\Program Files\Olive).

Additional Information

Don't remember having this problem with the old version (i.e., the version whose files are not compatible with the new version anymore).

Im not entirely sure this is an "olive" issue, I would recommend running a stress test, you may be hitting a variety of issues.

do you get a bsod If yes what is there error?

is your laptop plugged into wall power?

can you collect windows event logs and send them? https://www.ibm.com/support/pages/exporting-windows-event-logs-event-viewer

Thanks. There is no blue screen of death, only a complete and immediate shutdown. Laptop is plugged into wall power and fully charged. This is the only scenario in which this problem occurs. Will try getting the logs later.