The VideoLAN Forums

Steps to reproduce problem
1. Start VLC
2. Close VLC
3. you'll see a VLC media player stopped working in reliability history (Control Panel\All Control Panel Items\Security and Maintenance\Reliability Monitor).
You'll not see any dialog box of stopped working, just one entry in reliability history. VLC version 3.0.0 works fine but I'm seeing an entry in reliability monitor whenever I close VLC. The problem is with both 32-bit and 64-bit version of VLC

Here are the problem details copied from reliability monitor

Source
VLC media player

Summary
Stopped working

Date
‎2/‎10/‎2018 10:03 AM

Status
Not reported

Description
Faulting Application Path: C:\Program Files\VideoLAN\VLC\vlc.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: vlc.exe
Application Version: 3.0.0.0
Application Timestamp: 00dee6e6
Fault Module Name: vlc.exe
Fault Module Version: 3.0.0.0
Fault Module Timestamp: 00dee6e6
Exception Code: c0000005
Exception Offset: 0000000000021860
OS Version: 10.0.16299.2.0.0.256.48
Locale ID: 1033

Are you on Windows 10 ? Can you try with the video output direct3d9 ?

Thanks, Bro.
I'm using windows 10 build 16299. I tried changing video output to Direct3D9 videos play smoothly. Even automatic mode plays video smoothly. The problem is not with playing video or audio files.
I'm seeing VLC media player under the critical event list. Every time I close VLC, VLC is added to the critical event list.
For example. Right now it's 7

I open VLC and close VLC. Now it's 8

By the way, VLC runs smoothly no problem in playing audio or videos.

I noticed one thing when the video is playing and I close VLC then VLC closes without any problem i.e. no entry in the critical event list.
The problem occurs when VLC is not playing anything and I closes it. I see one more entry in critical event list

Seeing this exact issue over here as well. VLC seems to function normally and even appears to exit gracefully with no apparent error message. Reliability Monitor, however, reports several VLC crashes that seem to only happen upon exit. On Windows 10 16299 running VLC 3.0 64 bit.

Edit: I should also note that I have reset preferences and cache and have also reinstalled multiple times.

OK. That's very weird

I needed you to test D3D9 vs D3D11, because we have a LOT of crashes on D3D11 on exit in our logs...

But it seems to be something else.

The output setting has not impact on my crashes. In disabled mode I also get them. It happens without playing anything. Open vlc then close vlc gives a crash.

Edit: Right now I can trigger the crash everytime I don't play anything. If I start a video and then close vlc then no crash.

I can confirm I have the same thing. Just oping/closing VLC 3.0.0 64 bits.

Is playlist visible when you open it ?

The issue is with both 32 bit & 64 bit of VLC media player on Windows 10 build 16299 x64 bit.


When I open VLC


Playlist is visible when I press ctrl + L or click view --> playlist

This issue is not present in this version (vlc-4.0.0-20180212-0513)
https://nightlies.videolan.org/build/wi ... 0212-0311/
https://nightlies.videolan.org/build/wi ... 0212-0513/

This issue is not present in this version (vlc-4.0.0-20180212-0513)
https://nightlies.videolan.org/build/wi ... 0212-0311/
https://nightlies.videolan.org/build/wi ... 0212-0513/

hi
in short we need to wait an update right?
vlc v4? they have just released v3
i guess to see a v3.1
i run w10 pro 64bit last update (no fast ring)
thanks

hi
in short we need to wait an update right?
vlc v4? they have just released v3
i guess to see a v3.1
i run w10 pro 64bit last update (no fast ring)
thanks

yes, I also think we need to wait for an update
but you can use version 4.0
I'm using version 4.0 (uninstalled 3.0). It has all the feature of version 3.0 and it is less buggy (could not encounter any problem till now)
thanks

I can CONFIRM same issue here.
- Windows 10 Professional (1709) - 16299.248
- VLC 64bits 3.0.0
- Lenovo Yoga 2 Pro (20266)
- Dell Optiplex GX620 MT

================================

Description
Faulting application name: vlc.exe, version: 3.0.0.0, time stamp: 0x00dee6e6
Faulting module name: vlc.exe, version: 3.0.0.0, time stamp: 0x00dee6e6
Exception code: 0xc0000005
Fault offset: 0x0000000000021860
Faulting process id: 0x8d8
Faulting application start time: 0x01d3a50ef913a3fe
Faulting application path: C:\Program Files\VideoLAN\VLC\vlc.exe
Faulting module path: C:\Program Files\VideoLAN\VLC\vlc.exe
Report Id: 455b6c78-2eba-4a95-96b5-1c85c7ba9832
Faulting package full name:
Faulting package-relative application ID:

================================

Description
The program vlc.exe version 3.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 3d50
Start Time: 01d3a50f2814fcd9
Termination Time: 34
Application Path: C:\Program Files\VideoLAN\VLC\vlc.exe
Report Id: 9b9b9b7e-ca9a-4dfa-9d3d-5b057a974243
Faulting package full name:
Faulting package-relative application ID:

================================

Please fix it ASAP.

Regards,

I uninstalled 64bits version and installed 32bits (VLC 3.0.0).
Same issue crashing and logging error event.

================================

Description
Faulting application name: vlc.exe, version: 3.0.0.0, time stamp: 0x00dee6e6
Faulting module name: vlc.exe, version: 3.0.0.0, time stamp: 0x00dee6e6
Exception code: 0xc0000005
Fault offset: 0x00023393
Faulting process id: 0x1dbc
Faulting application start time: 0x01d3a5bbff0f763c
Faulting application path: C:\Program Files (x86)\VideoLAN\VLC\vlc.exe
Faulting module path: C:\Program Files (x86)\VideoLAN\VLC\vlc.exe
Report Id: 72852c0a-f1be-43c2-b9db-240169df5c81
Faulting package full name:
Faulting package-relative application ID:

================================

NOTE: VLsub (version 0.9) CRASHING also when searching subtitles.

Please fix it ASAP.

We cannot promise that it is or will be fixed without a stack trace. One major crash source was fixed today, but I cannot tell if that was your problem from your posts. You will have to try a nightly yourself.

The problem is gone in 3.0.1

This is now fixed, but the problem wasn't present in nightly builds. 3.0.1 release will be fine.

Thank you
any release date for 3.0.1