[Windows] launch.exe crash at random (usually while previewing a video)

[nwgat]

launch.exe crash when opening a h264 mp4 or mkv file

OpenShot 2.0.4 Windows 10 x64

i can post log, if only i knew where it was

[cloverpi]

Also getting this crash when working with 1080p. Debugging ASM shows a program break at:

07FE719C rep movs byte ptr es:[edi],byte ptr [esi]

Original break message was access denied at memory offset 0x0000000 - libopenshot.dll. Bad pointer perhaps?

[DVLP]

same here, crashes on 1080p export, freezes at 1% on 720p export source files are 1080p 30fps MOV videos from my GoPro knockoff "DBPOWER"

win 10, 64bit, latest version

[Anorionil]

I also have consistent crashes on Windows 10.

• When dragging a file from a folder into the program, but hovering over the timeline, not the project files
• When trying to preview or render a video with increased speed (2X) effect.

preview_thread:INFO initPlayer
 main_window:ERROR Unhandled crash detected... will attempt to recover backup project: C:\Users\<>\.openshot_qt\backup
    tutorial:INFO process tutorial dialogs
         app:INFO Process command-line arguments: ['C:\\Program Files\\OpenShot Video Editor\\launch.exe']
 main_window:INFO updateStatusChanged

[Dattaya]

On Windows (10) Openshot 2.1.0 is completely unusable for me—constant crashes, it freezes while exporting a video.

[apraetor]

OpenShot on Win10 starts causing a ton of disk activity on C: prior to crashing this way during export (source and destination drives are both independent disks, and NOT C:). I have 16 GB of RAM available to OpenShot, so maybe there's a leak?

I've noticed an interesting coincidence during export: OpenShot starts with about 2.8 GB of memory used during an export (for me, H.264 to H.264, video simply split). Memory usage slowly climbs to 3.3 GB, at which point it drops to 1.7 GB instantly (well, <= 1 second) and Windows begins reporting OpenShot as "Not Responding. Over 10 seconds the memory usage climbs back to 2.8 GB, Windows reports OpenShot is "Running" and.. rinse, lather repeat. Sometimes this cycle proceeds until 100% export and I have a usable video, but 9/10 times Windows decides it has had enough and decides OpenShot has crashed. During the hangs there is no disk IO, which was what I'd first suspected might be blocking.

[wgaylord]

I have this same problem... (on windows on my ubuntu install it works fine.)

[Hjallis]

Same Problem; OpenShot "Launch.exe" crashes on windows 10 as soon as I try to Export the Video openshot-qt.txt

[mixiekins]

Ditto on the Launch.exe crash at export. Didn't see any spike in resource usage when attempting to export, it crashes immediately when proceeding to create the export file (which ends up being 0 bytes). It does consistently crash as soon as I try. I'm attempting to export a pretty simple project consisting of 5 very short .MP4's with the preset export profile Web > YouTube (tried each of all the quality options).

Fresh install of OpenShot build v2.2.0-x86_64. Windows 7 Pro; Service Pack 1, 16 GB ram. openshot-qt.txt

¯_(ツ)_/¯ Really at a loss on this one, not sure what else to give. Hope this helps.

[wgaylord]

I gave up on open shot considering both the Linux and windows versions crash randomly and can't export a file that does not studder.

[mixiekins]

Same, I found that there's actually a fairly serviceable editor in youtube.com/editor that lets you splice together footage if you upload it (can be set to private). Gets the job done, but I'd really like to use openshot.

[wgaylord]

I end up doing my video editing on Linux using one of the free ones. Open shot took 60 min to render the one I use took 13 min. Granted openshot keep freezing and almost crashing.

Sent from my iPad

On Jan 17, 2017, at 11:05 AM, Cari notifications@github.com wrote:

Same, I found that there's actually a fairly serviceable editor in youtube.com/editor that lets you splice together footage if you upload it (can be set to private). Gets the job done, but I'd really like to use openshot.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[rob-lindman]

just reporting that the same thing many people above happens to me under Win10 x64. It crashes at random. After the last crash it just crashes upon opening. This of course sucks because when it does work it is actually really cool. Only program that can take a video and play it backwards. :(

[dancetheskies]

I share your disappointment with Open Shot for Windows. Every release (and I’ve tried them all from the very beginning about two years ago) crash under Windows (7, 8 and 10). I use MAGIX Movie Edit Pro for tasks such as reversing a Movie. It a commercial program, not open source donation-supported software, but it does actually work without crashing.

From: Rob Lindman Sent: Sunday, February 26, 2017 9:32 PM To: OpenShot/openshot-qt Cc: dancetheskies ; Mention Subject: Re: [OpenShot/openshot-qt] [Windows] launch.exe crash at random (usually while previewing a video) (#13)

just reporting that the same thing many people above happens to me under Win10 x64. It crashes at random. After the last crash it just crashes upon opening. This of course sucks because when it does work it is actually really cool. Only program that can take a video and play it backwards. :(

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[wgaylord]

@jonoomph Can you fix this yet??? its been forever and nothing has changed still randomly carashes then won't run at all afterwards.

[wgaylord]

It's been over a year an @jonoomph has not been able to solve this bug. Which makes openshots unusable on Windows 10 x64. What gives? Like really.

[jonoomph]

@chibill This ticket might have been on the back burner (clearly), but we've made huge improvements to stability and performance in the past 60 days, especially with Windows. Please verify these crashes still happen with our latest daily build for Windows: Please visit www.openshot.org/download, click 'Other Downloads', and install the latest daily build of OpenShot.

If the crash still happens, please see these instructions (https://github.com/OpenShot/openshot-qt/blob/master/.github/CONTRIBUTING.md) for attaching logs, and re-open this ticket. If you have other issues not related to the launch.exe crash bug, please file as new bugs. Thanks!

[mixiekins]

Hiya, @jonoomph Well, I've downloaded the newest version right after I got your update here, it's been going for about 20 mins with this message: I let it keep going, assuming that Windows is misinterpreting it as having crashed rather than giving a progress bar, but I've been using openShot for years now (Linux version under Debian) and never found it to take this long to render such a small project, so I suspect it's still an issue. Hope this helps, and thanks! logs.zip

[rob-lindman]

completely absurd to close this issue. I redownloaded and installed the whole program two days ago and it's as crash happy as ever. and once it crashes, then reopening it puts it into 'reload the failed project', and it crashes. and then I delete the failed project from the data folder, and relaunch it, and try to do things with it such as, oh, I don't know, edit video, and it crashes. Just to verify this, I opened it, loaded a perfectly good video file, went to export, picked Youtube, started the export, and it got to 2% before it crashes. This is Windows 10. 2.1.0.dev-1. I would love to use this program. It's worked before and it has a great interface and it looks like great effects... being able to play things backwards is magic I need. But it's infuriating and causes anxiety to wonder if with every click of the mouse it's going to crash somehow.

[maritz]

@rob-lindman Could you please attach some log files. This is obviously something he cannot reproduce on his machine, so debugging is difficult and having as many crashlogs as possible is very helpful.

[pexaorj]

The same bug here. In the first version of openshot I did not have this issue.

[wgaylord]

Same here... And when it does work it takes for ever and apparently people can't read what I type when I type a resolution.

[pexaorj]

The strange thing is that in the first version of software, it is working fine and then when I update, this not work anymore :( The bad thing is when I try to open, this show this message and I can not open the openshot anymore.

[dancetheskies]

I have D/L the nightly builds the last several days, and I am having none of that failure to launch error problem any more on my W10 x64) PC now! I've actually been able to work with some of the editing functions now and export clips with decent rendering time. I've made some short animated "intro" clips with the "exploding" and "dissolving" title creation tools. I don't know what might have changed in the very recent nighty builds, but I'm starting to think I can actually do some efficient editing with OpenShot now!

The nightly builds can be accessed via the regular download link, but ignore the released version and click on the "other Windows downloads" link to get the latest beta version.

Am I the only one that these recent builds now seem to work well for?

[wgaylord]

I have been able to get the to work. But that does not fix the fact that they still randomly crash. (At least you can relaunch it now) but my issue now is its fast to use movie maker then this... (Easier too)

On Mar 21, 2017 9:38 PM, "dancetheskies" notifications@github.com wrote:

I have D/L the nightly builds the last several days, and I am having none of that failure to launch error problem any more on my W10 x64) PC now! I've actually been able to work with some of the editing functions now and export clips with decent rendering time. I've made some short animated "intro" clips with the "exploding" and "dissolving" title creation tools. I don't know what might have changed in the very recent nighty builds, but I'm starting to think I can actually do some efficient editing with OpenShot now!

The nightly builds can be accessed via the regular download link, but ignore the released version and click on the "other Windows downloads" link to get the latest beta version.

Am I the only one that these recent builds now seem to work well for?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OpenShot/openshot-qt/issues/13#issuecomment-288281300, or mute the thread https://github.com/notifications/unsubscribe-auth/ACCNyXAhmtSM1y1cGXk7cYgH6t6wpnPoks5roIm1gaJpZM4HCUni .

[pexaorj]

Now I downloaded the last version: OpenShot-v2.2.0-62-gf96ab26-49-615-x86_64.exe (March 21, 2017, 5:01 p.m.)

And works fine for me.

So I will still evaluate and then post the result here.

Thanks for all support until now 👍

[mixiekins]

No luck here, the bug is persisting. Tried OpenShot-v2.2.0-62-gf96ab26-49-615-x86_64.exe (March 21, 2017, 5:01 p.m.) just now and confirm that the problem I described earlier in this thread is unchanged.

logs.zip

[openmn]

Before you install latest version, make sure you have completely removed any older versions.

OpenMN

On Mar 21, 2017 11:18 PM, "Cari" notifications@github.com wrote:

No luck here, the bug is persisting. Tried OpenShot-v2.2.0-62-gf96ab26-49-615-x86_64.exe (March 21, 2017, 5:01 p.m.) just now and confirm that the problem I described earlier in this thread is unchanged.

[image: image] https://cloud.githubusercontent.com/assets/7697278/24181999/8cfdf182-0e8c-11e7-80f7-a16357303b76.png logs.zip https://github.com/OpenShot/openshot-qt/files/860320/logs.zip

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/OpenShot/openshot-qt/issues/13#issuecomment-288294530, or mute the thread https://github.com/notifications/unsubscribe-auth/AQepbBYp9HLGgzPOjLm7Quxwvk_Mic4Kks5roKEhgaJpZM4HCUni .

[apraetor]

The latest release (OpenShot-v2.2.0-65-g5a9712d-49-615-x86_64.exe) works well for me. I haven't had a chance to test it extensively yet, but I no longer get crashes if I don't drag clips into OpenShot in a very particular manner. I will test it with longer encode operations this evening.

One thing of note: if I start a new project, then close OpenShot and click "No" on the "Do you wish to save before exiting?" dialog.. OpenShot hangs indefinitely and pulls 100% CPU.

[kenmaglio]

Having the same issue, never used this software before, and I'm struggling to keep using it with this crash. I've had to set my autosave down to seconds, just to ensure I don't loose work.. This is really frustrating.

I love how this is a closed issue too... thanks for Windows support.

And because I have Visual Studio I hit debug, and got additional debug information on the crash event:

Unhandled exception at 0x000000018073CE25 (avcodec-57.dll) in launch.exe: 0xC0000005: Access violation reading location 0x00000000000000F0

[wcphart]

August, this is still happening. Guess this gets added to the do not use list....

[wgaylord]

I think openshot just does not wish to support windows.. :(

Sent from my iPad

On Aug 9, 2017, at 5:57 PM, wcphart notifications@github.com wrote:

August, this is still happening. Guess this gets added to the do not use list....

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[suwidadi]

Having same issue. i event reinstall display driver and uninstall vc++ prior to 2015 but still no luck.

[floydianslips]

I am having the same issue on Win10 64-bit. It clears when I remove the /.openshotqt directory. However when I attempt to open the same project it throws the same error. My guess is it must be a corrupted project file. Luckily it was a small project that I can do again in short order. I will attach the logs. Thanks for this great product and let me know if I can do any other testing. I can give you access to the corrupt file as well if you want.

libopenshot.log openshot-qt.log

[kem1]

I am not sure it's the same issue but I have serious troubles with launch.exe as well in the latest version 2.4.1 on Win7 64 & quite powerful machine. symptoms:

• launch.exe fully occupies single thread (running maximum capacity of single thread almost all the time)
• 99% of time the GUI is in state (Not Responding) but not crashed. I am waiting for any action in GUI long minutes (e.g. 10 minutes)

It's not only annoying. It prevents any useful work with OpenShot. I just wonder if anyone experienced same issue. I suppose the issue could be with some type of input files (mp4?) or when the sources are large (e.g. 150 MB video)?