Join GitHub today
Download Video Player Mfc Application Stopped. Devices and interfaces. DRIVERS & SOFTWARE. Download drivers. Especially game programming and video. WinDVD 9: WinDVD MFC Application has stopped working. So looks like the software has no functionality for me, WinDVD can't play a DVD.
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upHave a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
commented Jan 11, 2016
launch.exe crash when opening a h264 mp4 or mkv fileOpenShot 2.0.4 Windows 10 x64 i can post log, if only i knew where it was |
commented Jan 11, 2016
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. |
commented Jan 11, 2016
it crashes when playing file, i can add them to timeline but when playing it back it will crash openshot-qt.log.txt |
commented Jan 11, 2016
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 |
commented Jan 12, 2016
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. =) |
commented Jan 12, 2016
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... |
commented Jan 12, 2016
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 |
commented Jan 12, 2016
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). |
commented Jan 12, 2016
i get the bugs when reading the file, like when you playing the timeline, exporting, and sometimes when playing it back from library |
commented Jan 12, 2016
it works for some reason on my laptop, is there a specific visual C++ runtime we need? |
commented Jan 13, 2016
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! |
changed the title[Windows] launch.exe crashJan 13, 2016
commented Jan 13, 2016
@Axxando@dancetheskies do you guys have blender installed? |
commented Jan 13, 2016
just got it to crash inside a super clean VM that basicly has only windows 10 x64, virtualbox tools and openshot installed |
commented Jan 13, 2016
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 |
commented Jan 13, 2016
@nwgat I have whatever the Windows installer provides. There's a populated Blender folder in the Openshot folder, so I assume I have everything.. |
commented Jan 14, 2016
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) |
commented Jan 14, 2016
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. =) |
commented Jan 14, 2016
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. |
commented Jan 14, 2016
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 FilesBlender FoundationBlenderblender.exe |
commented Jan 14, 2016
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... |
commented Jan 14, 2016
back to issue do this on clean windows setup
Video: http://awesome.nwgat.ninja/misc/openshotbug2.webm |
commented Jan 15, 2016
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) |
commented Jan 15, 2016
Here is some small y4m 4k clips you can try shovel thru your self ;P unxz file.xz |
commented Jan 15, 2016
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). |
commented Jan 15, 2016
@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 |
commented Jan 15, 2016
@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 |
commented Jan 17, 2016
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 |
commented Jan 17, 2016
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:Windowssystem32en-USerofflps.txt |
commented Jan 17, 2016
@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. =) |
commented Jan 17, 2016
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 |
commented Nov 29, 2016
Same Problem; OpenShot 'Launch.exe' crashes on windows 10 as soon as I try to Export the Video openshot-qt.txt |
commented Jan 17, 2017
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. |
commented Jan 17, 2017
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. |
commented Jan 17, 2017
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. |
commented Jan 17, 2017
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. … On Jan 17, 2017, at 11:05 AM, Cari ***@***.***> 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. |
commented Feb 27, 2017
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. :( |
commented Feb 27, 2017
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 LindmanSent: Sunday, February 26, 2017 9:32 PMTo: OpenShot/openshot-qtCc: dancetheskies ; MentionSubject: 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. |
commented Feb 27, 2017
@jonoomph Can you fix this yet??? its been forever and nothing has changed still randomly carashes then won't run at all afterwards. |
Video Player Mfc Application
commented Mar 2, 2017 • edited
edited
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. |
commented Mar 2, 2017
@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! |
commented Mar 2, 2017
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 |
commented Mar 2, 2017 • edited
edited
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. |
commented Mar 2, 2017
@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. |
commented Mar 22, 2017
The same bug here. In the first version of openshot I did not have this issue. |
commented Mar 22, 2017
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. |
commented Mar 22, 2017
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. |
commented Mar 22, 2017
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? |
commented Mar 22, 2017
I have been able to get the to work. But that does not fix the fact thatthey still randomly crash. (At least you can relaunch it now) but my issuenow is its fast to use movie maker then this... (Easier too) …On Mar 21, 2017 9:38 PM, 'dancetheskies' ***@***.***> 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 <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACCNyXAhmtSM1y1cGXk7cYgH6t6wpnPoks5roIm1gaJpZM4HCUni> . |
commented Mar 22, 2017
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 |
commented Mar 22, 2017
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 |
commented Mar 22, 2017
Before you install latest version, make sure you have completely removedany older versions.OpenMN …On Mar 21, 2017 11:18 PM, 'Cari' ***@***.***> 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 <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQepbBYp9HLGgzPOjLm7Quxwvk_Mic4Kks5roKEhgaJpZM4HCUni> . |
commented Mar 22, 2017
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. |
commented May 25, 2017 • edited
edited
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 |
commented Aug 9, 2017
August, this is still happening. Guess this gets added to the do not use list.... |
commented Aug 9, 2017
I think openshot just does not wish to support windows.. :( … On Aug 9, 2017, at 5:57 PM, wcphart ***@***.***> 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. |
commented Aug 25, 2017
Having same issue. i event reinstall display driver and uninstall vc++ prior to 2015 but still no luck. |
commented Sep 27, 2017
Windvd Mfc Application Error
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 |
Closed
commented Feb 7, 2018
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:
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)? |
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
Windows 8 is more forgiving with regard to application compatibility than some of the previous versions of Windows were, but some applications just will not work with it. Thankfully, you don't always have to accept defeat. Although there is no silver bullet that guarantees application compatibility, you can use a number of tricks to improve your odds of getting a stubborn application to run in Windows 8.
1: Create a virtual machine
I will go ahead and get the last resort step out of the way up front. Windows 8 includes its own copy of Hyper-V. If you can't get an application to function in Windows 8, you can enable Hyper-V and create a virtual machine running a legacy version of Windows as a way of running the application.
2: Turn off User Account Control
I haven't experienced any User Account Control (UAC)-related compatibility problems in Windows 8 yet, but I have run into problems in Windows 7. When I first adopted Windows 7, there was a particular dictation application that would not work until I disabled UAC. I have read posts on the Internet from people who have had similar experiences in Windows 8, where disabling UAC resolved a compatibility issue.
3: Install .NET Framework 3.5
When you install Windows 8, version 4.5 of the .NET Framework is installed by default. However, older apps often require an earlier version of the .NET Framework. If you receive a .NET Framework-related error, you can go into the Control Panel, click on Programs, and choose the option to turn a Windows feature on or off. Windows will display a list of the various components you can enable or disable. One of the items on the list is .NET Framework 3.5, which also includes .NET 3.0 and 2.0. Installing this component will likely correct the issue that you are experiencing.
4: Check for application patches
![Download Download](https://www.bcgsoft.com/Images/screenshot-6.jpg)
One of the first things you should do upon discovering an application compatibility problem is contact the application vendor and find out if it has a Windows 8 patch available. Sometimes, a patch is all you need.
5: Upgrade to the next version
When I made the switch to Windows 8, I discovered that a video-editing application I use on a regular basis would not work with Windows 8. Although I might have been able to resolve the problem using less drastic measures, I ultimately decided to simply upgrade to the newest version of the application. Not only was the latest version certified to work with Windows 8, but it also had some other new features I wanted to try out.
6: Upgrade your hardware drivers
One of the biggest problems I had when I upgraded to Windows 8 was that a program I use every day wouldn't run. The error message I received indicated that Windows 8 did not support OpenGL. However, OpenGL support is provided by the video driver, not by the operating system. It turned out that my problem was caused by an outdated version of AMD Catalyst. When I upgraded to the latest version, the problem went away and I was able to run the application.
7: Let Windows troubleshoot the problem
Windows 8 includes a utility called the Program Compatibility Troubleshooter that can sometimes automatically resolve compatibility problems. You can run the Program Compatibility Troubleshooter by right-clicking on the problematic application and choosing the Troubleshoot Compatibility command from the shortcut menu.
8: Trick the application into thinking it is running on an earlier version of Windows
Some applications are hard-coded to look for a specific version of Windows. In these types of situations, you can configure Windows 8 to lie to the application about what version of Windows you're running. Start by running the Program Compatibility Troubleshooter (as described above). When you get to the What Problems Do You Notice screen, choose the option for programs that worked in an earlier version of Windows. After clicking Next, you will have the option of telling the utility which version of Windows the application worked in.
9: Provide the application with extra permissions
Some legacy applications (especially those written for Windows XP) fail to run due to inadequate permissions. Once again, the Program Compatibility Troubleshooter can help. When you get to the What Problems Do You Notice screen, choose the option related to the program requiring additional permissions. As an alternative, you could try right-clicking on the application and choosing the Run As Administrator option (assuming that you have administrative permissions).
10: Check the Compatibility Center
One last thing you can do is check the Compatibility Center for information about the application. The Compatibility Center is a Web site Microsoft uses to provide application compatibility information for Windows 7 and 8. In some instances, it provides a link to detailed instructions on what you must do to make an otherwise-incompatible application work with Windows 8.
Top 10 Newsletter
Turn to these must-read primers to get the skinny on the hottest tech topics, strategies, and analyses. Delivered Fridays