OpenShot / openshot-qt

OpenShot Video Editor is an award-winning free and open-source video editor for Linux, Mac, and Windows, and is dedicated to delivering high quality video editing and animation solutions to the world.
http://www.openshot.org
Other
4.33k stars 537 forks source link

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

Closed nwgat closed 7 years ago

nwgat commented 8 years ago

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

image

OpenShot 2.0.4 Windows 10 x64

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

jonoomph commented 8 years ago

The log is located in your home folder: /Users/YOURUSER/.openshot_qt/

Does OpenShot crash on launch? Or only after you drop in these particular media files? If you have a small, sample file that crashes OpenShot, please attach it as well.

nwgat commented 8 years ago

it crashes when playing file, i can add them to timeline but when playing it back it will crash openshot-qt.log.txt

nwgat commented 8 years ago

samples

wget -U "QuickTime/7.6.2" http://trailers.apple.com/movies/independent/ratchetandclank/ratchetandclank-tlr1_h1080p.mov

wget -U "QuickTime/7.6.2" http://trailers.apple.com/movies/summit/nowyouseeme2/nowyouseeme2-tlr1_h1080p.mov

jonoomph commented 8 years ago

Both of these files work great for me on Linux. I'll test them on Windows soon, and see if that crashes for me. Also, you might try setting your profile to 1080p 24fps, which will have better performance and match the video files. I'll update this tomorrow with some Windows testing. =)

Axxando commented 8 years ago

I don't think it's related to the files you load. I have it installed on 2 machines (one Win7 and one Win10) and they crash with this error message after a (felt) random period of time unrelated to what I do...

nwgat commented 8 years ago

for me it seems related to reading the video file everytime i play it back or put it on the timeline and then play that it crashes

dancetheskies commented 8 years ago

I have the same experience as Axxandro on my W10 (x64) PC. The program crashes shortly after I do anything with the generic "launch.exe has stopped working" alert. An exception is when I tried to do a PIP by slicing a video, putting one part on a second track, changing the layout of one clip to 1/4 size, then trying to play both at the same time. That generates the C++ runtime error crash alert shown above.

I like what I'm seeing with the general program structure, but until I can actually complete some editing, I can't isolate specific bugs. Even loading in a video (h.264 or h.265) and simply saving it back out as an h.264 clip will crash with the launch.exe crash alert.

I also have a few wish list items, but this does not look like the place to mention them (at least for now).

nwgat commented 8 years ago

i get the bugs when reading the file, like when you playing the timeline, exporting, and sometimes when playing it back from library

nwgat commented 8 years ago

it works for some reason on my laptop, is there a specific visual C++ runtime we need?

jonoomph commented 8 years ago

It does ship on Windows with a VC++ runtime, but it packages up what it needs, and doesn't use the system ones (to the best of my knowledge).

I've tested the video files linked above on Windows 10, and everything works fine for me. I got no crashes on Windows 10 or Ubuntu 14.04. If I had to take a huge guess, I would say we have some kind of race condition happening, where every once in a while, something happens in an unexpected order.

In order to track this down, it would be helpful if we can nail it down to a specific thing. For example, if all you do is watch the video, over and over again. Or all you do is grab the edge of the clip, and drag it left and right. Or move the clip when the playhead is overlapping it (back and forth, dropping it each time on the timeline).

So, instead of using the app like normal, I'm suggesting using it in very 1 dimensional ways, so we can start to eliminate certain things. Good luck and thanks for helping me track these things down!

nwgat commented 8 years ago

@Axxando @dancetheskies do you guys have blender installed?

nwgat commented 8 years ago

just got it to crash inside a super clean VM that basicly has only windows 10 x64, virtualbox tools and openshot installed

nwgat commented 8 years ago

video of VM http://awesome.nwgat.ninja/misc/openshotbug.webm i think it can be related to the buffer underflow in ffmpeg that was reported on linux

dancetheskies commented 8 years ago

@nwgat I have whatever the Windows installer provides. There's a populated Blender folder in the Openshot folder, so I assume I have everything..

Axxando commented 8 years ago

Blender is installed on the Win7 machine Blender is not installed on the Win10 machine (but there's the above mentioned folder "blender" within openshot)

jonoomph commented 8 years ago

Blender is not packaged with OpenShot... just some blender templates and scripts, but they still require the user to install Blender, and then update the preferences in OpenShot to point to the Blender executable. I hope that explains it better.

Also, Blender is only invoked when rendering 3D Animated titles, so unless you are getting a crash on that screen, it's probably not related to Blender. =)

dancetheskies commented 8 years ago

I would never have known this... maybe ought to include it in the Windows installer or at least provide a ReadMe.txt file or something so we know bout it. Where do I download Blender? My Preferences just shows "blender" as the path, which is not a full path name to me. Does it go in the Blender folder that the Windows installer creates, or should this show a full drive/path name to it (if it creates one when I install it?

I've not tried to use any titles, yet, so this has nothing to do with the crashes. But it would have created problems later, so thanks for the clarification.

nwgat commented 8 years ago

to use blender on windows you need to use full path and most of the advanced titles needs it meybe have a checkbox or something in the installer?, do you want to install inkscape/blender

blender download: http://mirror.cs.umn.edu/blender.org/release/Blender2.76/blender-2.76b-windows64.msi path for openshot: C:\Program Files\Blender Foundation\Blender\blender.exe

dancetheskies commented 8 years ago

Thanks. I had done a search after I posted and got this this point, then found that there is an alert in OpenShot that pops up when 3D titles option is selected giving this information as well! The only difference is the path it shows in to put in preferences which does not include the "blender.exe" on the end. I'll test it to see to see...

nwgat commented 8 years ago

back to issue do this on clean windows setup

  1. import ratchetandclank-tlr1_h1080p.mov
  2. drag it to timeline
  3. export video
  4. choose all formats > webm
  5. watch it crash

Video: http://awesome.nwgat.ninja/misc/openshotbug2.webm

nwgat commented 8 years ago

well this is how it looks when i try* shovel a 4K video thru openshot notice the amount of dialogs and the amount of timelines that are the default 5 (0-4)

nwgat commented 8 years ago

Here is some small y4m 4k clips you can try shovel thru your self ;P unxz file.xz

dancetheskies commented 8 years ago

I get similar multiple runtime crash alerts along with the general "launch.exe has stopped working" alert by simply loading an h.264, 1080p-30fps, .mp4 video, dragging it to the time line, then trying to export a new re-encoded version (still keeping it as an H.264, 1080p-30fps, .mp4 clip). h 264 mp4 video

nwgat commented 8 years ago

@dancetheskies i also get the launch.exe dialog too, it just wasnt in the picture and btw i think one of the runtime dialogs are behind one of them, so you do have 5 of them just that 4 is seen

nwgat commented 8 years ago

@jonoomph btw you can download windows 10 eval iso and install it under Virtualbox to test a clean windows setup

i suspect you might have a bunch of libs, tools, dev tools, etc on your windows machine

nwgat commented 8 years ago

just tested it in a VPS on windows 2012, got it to crash again and i think i was right to suspect ffmpeg as its libvpx that crashes

Problem signature: Problem Event Name: APPCRASH Application Name: launch.exe Application Version: 0.0.0.0 Application Timestamp: 549dea3c Fault Module Name: libvpx-1.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 001fc3d0 Exception Code: c0000005 Exception Offset: 000c0a70 OS Version: 6.3.9600.2.0.0.400.8 Locale ID: 1033 Additional Information 1: 5861 Additional Information 2: 5861822e1919d7c014bbb064c64908b2 Additional Information 3: a10f Additional Information 4: a10ff7d2bb2516fdc753f9c34fc3b069

nwgat commented 8 years ago

another crash when encoding to All Formats > Mp4 > HDV 720 24p > High

Description: A problem caused this program to stop interacting with Windows.

Problem signature: Problem Event Name: AppHangB1 Application Name: launch.exe Application Version: 0.0.0.0 Application Timestamp: 549dea3c Hang Signature: d2f1 Hang Type: 134217728 OS Version: 6.3.9600.2.0.0.400.8 Locale ID: 1033 Additional Hang Signature 1: d2f1ec8da3fdcc222bf4ed87a0db209e Additional Hang Signature 2: 3ffa Additional Hang Signature 3: 3ffaf2963ce8b4a0464f7b0c353af532 Additional Hang Signature 4: d2f1 Additional Hang Signature 5: d2f1ec8da3fdcc222bf4ed87a0db209e Additional Hang Signature 6: 3ffa Additional Hang Signature 7: 3ffaf2963ce8b4a0464f7b0c353af532

Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=280262

If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt

jonoomph commented 8 years ago

@nwgat Do you have 4 processors? You might be getting an error on each core, during some of the thread pooling (which tries to match the # of processors). I'm going to spend some extra time running OpenShot in Windows under the GDB debugger, and see if I can catch a crash. =)

nwgat commented 8 years ago

well i get 4 errors even on a 8-core and in a 4-core virtualbox vm i think the thread pooling dont work above 4-core

nwgat commented 8 years ago

update for 2.0.5 (beta 2), error still there, i get four visual runtime errors and the launch.exe has stopped working

dancetheskies commented 8 years ago

Confirmed... very disappointing for Windows users after such a very long wait. I hope this can be resolved soon so we can actually start testing all the features.

nwgat commented 8 years ago

@jonoomph would been great if you released a debug version, that way it will be simpler to figure out what crashes on different systems

jonoomph commented 8 years ago

We'll get this figured out! It's hard to fix something if I can't reproduce it though. It obviously sounds like something is breaking with libvpx... I'm going to double check some things about my packaging, and be sure I'm including the correct version of libvpx. Thanks!

For what it's worth, I've tested both beta installers on 2 different computers running Windows 10, and can not reproduce this issue.

jonoomph commented 8 years ago

I have found a couple crashes on Windows, that don't seem to happen on the other platforms. I've already fixed them, and plan on releasing a new beta soon. Thanks for everyones patience!

dancetheskies commented 8 years ago

openshotcrash

I guess I'll be the first to report I'm still getting the launch.exe and C++ Runtime error messages when I do anything after I load a file into the new V3 beta OpenShot. Loading a video file (a 1080p-60fps .mp4 clip with AVC encoding) will crash about 1.5 sec after simply trying to play it. Anything else also causes similar crashes. Sigh.... :-(

I guess I should add I'm running W10.0 (build10240), fully updated with everything MS pushes to it. They have not pushed the Nov. 2015 major OS update yet though. I did an advance D/L of it last fall, and it was not working properly on my MS SurfacePro 2 system, so I think it's not ready for primetime yet either.
fmcc5 commented 8 years ago

I'm using the new 2.0.6 version from your link in update 45 am getting a crash in windows 8.1 x64, I've only seen the launcher.exe has stopped working message and not a C++ Runtime Library message. Only crashes if video is 1920x1080, If the file is 1024x768 all is good. Even a small 3.4Mb 338kbps bitrate 1080p crashes. Crashes every time if I load file, put in track and watch. Can crash if I put in track and slice. Attached logs for crash for both types and a video that makes it crash AMPLITUDE Studios.mp4 and one that doesn't intro.mp4.

openshot-qt.log.slice.txt openshot-qt.log.watching video.txt AMPLITUDE Studios.zip intro.zip

dancetheskies commented 8 years ago

Interesting about only the 1080p video causing crashes. I tried both 720p-60fps and WVGA (848 x 480) videos at 60fps and I was able to play them on the time line. But when I started to slice them and drag together the saved slice pieces, I again got the launch.exe error. It's a real puzzle, for sure.

openmn commented 8 years ago

I am using 2.0.6 on Win7 x64 and I get a Launch.exe has stopped working any time I try and export. MOV, MP4, 720p30 or 640x480, crashes. I have yet to be able to export my video once. Let me know if I should create a new issue for this problem.

nwgat commented 8 years ago

@jonoomph any updates?, i can simply crash it on demand, is there any additional software that might be out of date? did QT or python change anything?

nwgat commented 8 years ago

@jonoomph any progress?

nwgat commented 8 years ago

am still getting it on 2.0.7 :( error

is there any c++ runtime installer we are missing?

when i play the 4k y4m file i get launch.exe error, but when i play from timeline with mov files i get the c++ error

dancetheskies commented 8 years ago

Nothing new from Jonathan for about 4 months! If he has not been incapacitated for some reason, I guess he gave up on a useable windows version? Jonathan ??

allthefoxes commented 8 years ago

Commenting here. Just gave OpenShot a try. Opened a random .mp4 file and just keep getting this error. Software is for the most part un-usable :(

allthefoxes commented 8 years ago

This is the latest version, and the release notes seem to say this was fixed? But it just never stops
01-8ab1

dancetheskies commented 8 years ago

Ditto for me as well. Boot new version... load generic h.264 /mp4 video, try to just play it in the editor.... bam... crashes with the same launcher stopped working error after just a few seconds. SIGHHhhhhhhhh....

I don't understand how Jonathan has it working on his machine, but no one else seems to be able to do it. I'm running W10 home (x64) latest 1511 build If it makes any difference.

maritz commented 8 years ago

Same stuff happening to me. Also not limited to 1080p, although 720p seems to last longer before it crashes. And by longer I mean dozens of seconds, but not minutes.

dwatts1772 commented 8 years ago

Switching to "Windows 8" in comparability mode allowed the video to play for a bit. But then when I clicked "pause" it threw up the same error.

nwgat commented 8 years ago

jonathan needs to run in on a new machine or a dual boot system, install windows 10 to another partition and only install openshot there, there must be something missing out of all the libraries

dancetheskies commented 8 years ago

I agree... something is very different about his test PC if he is not getting the almost immediate crashes we have been reporting. Open Shot is not even stable enough to try out a simple playback, let alone do any editing.... very disappointed with the (lack of) recent progress on fixing this.

From: nwgat Sent: Tuesday, July 12, 2016 3: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)

jonathan needs to run in on a new machine or a dual boot system, install windows 10 to another partition and only install openshot there, there must be something missing out of all the libraries

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

AndreyCorelli commented 8 years ago

2 different PC: Windows 8 x64, Windows 10 x64. The second PC has an almost clean Windows installed recently.

Both can't render my clip (a simple one). One PC has more RAM... it makes up to 40% Another one makes only 10%.

About 30 crashes for one hour while working on clip.. especially while playing the video.

The question is: can I export my project somewhere somehow to render it in a stable environment?