1.4.0: Crash after having read a MOV file

[Daz]

Subject: 1.4.0: Crash after having read a MOV file (generated by iPhone)

XnView: MP 1.4.0 - 64-bit
OS: Windows 11 - 64-bit

XnView crashes several seconds after having read a MOV file in a dedicated tab.

Effect: XnView crashes

To reproduce:
1. Browse a folder with a MOV file
2. Double click on the MOV file and read it in the opened tab (video reading is performed nominally).
3. Close the tab (click on the X button of the tab).
Actual behaviour (bug): XnView comes back to the original folder, seems to work a bit in the background (several seconds) and crashes

Expected behaviour: No crash.

[Gimald]

If it helps: I can confirm this bug.

I tested different ways to see if it can be avoided. Here some examples what I did:

In a folder, I had one mp4 (video) file and 10 images files.

1. I doubled clicked an image, opened in the browser, closed the tab: No crash

2. I double clicked a video, closed the tab: Crash

3. I double clicked an image, then clicked "next" to browse through the gallery, until I reached a video file. Then closed the tab: Crash

4. I double clicked an image, "next" until hit video, then went "next" again to go back to an image file. I closed the tab: Crash

Conclusion: once a video file was double-click opened, or even browsed (via "next" command) in the browser, and then the tab is closed, it will crash.

[xnview]

To reproduce:
1. Browse a folder with a MOV file
2. Double click on the MOV file and read it in the opened tab (video reading is performed nominally).
3. Close the tab (click on the X button of the tab).
Actual behaviour (bug): XnView comes back to the original folder, seems to work a bit in the background (several seconds) and crashes

are you able to reproduce each time? No crash in browser's preview?

[xnview]

2. I double clicked a video, closed the tab: Crash
3. I double clicked an image, then clicked "next" to browse through the gallery, until I reached a video file. Then closed the tab: Crash
4. I double clicked an image, "next" until hit video, then went "next" again to go back to an image file. I closed the tab: Crash

I can't reproduce, are you able to reproduce each time? do you have 'auto play' setting? No crash in browser's preview?

[Daz]

I can reproduce it each time.
If it may help, I tried with several versions and the bug is not present on v1.0 (it seems present on all other versions)

[Daz]

And yes the videos work perfectly with the Windows video player

[Gimald]

I can also reproduce it every time. When closing a Tab that displayed a video once, it crashes.
Same happens with Browser Tab. If I click on a video, and then close the Browser Tab, it crashes, too. Autoplay is off for me. Videos play, there is no problem with the playback. Only the tab closing crashes xnview mp, when a video was once selected/shown (dowsnt need to play the video. Only marked/shown is enough to make the software crash, when its tab is closed)

Browser Preview doesnt crash. Only when tabs are closed, including the Browser Tab, too, when once a video in the browser was selected. Its not a playback error I think. It is just, when a Tab detects that when (even only once) a video was ever selected in this tab (doesnt matter for how long this tab is now open, like you displayed a video on minute 3, now 3h passed, and only pictures were displayed afterwards), the software will crash when you close the tab, where at least one video was ever opened in that tab. Basically, only when closing the tab it happens, not during a preview play in the brother, nor during a tab play.

Is there a way to debug xnview mp? So I can check what error logs I get?

EDIT: Okay I think I found out the issue. It is a rather awkward issue. I had xnview mp installed on an older Laptop, which still had WIndows 10 1909 installed. Testing xnview on my device with Windows 10 21H2, everything worked. So I just updated 1909 on the laptop to 21H2 via Windows Updates (took a while to upgrade). Now it works there, too. I am not sure why it was this case.

It is possible it might have been a Driver issue maybe? Since after upgrading form 1909 to 21H2, my GPU drivers stopped working, saying, that this version of my GPu software isnt supported for this System. APU is form AMD. I suppose Amd gives different installations, depending on the WIndows Version. So, 1909 has differerent installaton compare dto 21H2 I guess?

Not sure how to help out the Original poster, since they seem to have Windows 11. But maybe your version is outdated, too? DId you try updating to cumulative 2022 - 12 december updates?

[xnview]

It is possible it might have been a Driver issue maybe? Since after upgrading form 1909 to 21H2, my GPU drivers stopped working, saying, that this version of my GPu software isnt supported for this System. APU is form AMD. I suppose Amd gives different installations, depending on the WIndows Version. So, 1909 has differerent installaton compare dto 21H2 I guess?

Perhaps, i've tried on Win 10 21H2 & Win 11 21H2, and i can't reproduce

[Daz]

Thank you for your tries but, unfortunately, it does not fix the issue for me. For information, my Windows 11 version is 10.0.22621.

I reverted back to version v1.0 to avoid the crash.

Is there any additional information that I can provide you to help solving the issue? Or some kind of logging that I could perform while reproducing the bug?

[xnview]

Is there any additional information that I can provide you to help solving the issue? Or some kind of logging that I could perform while reproducing the bug?

Are you able to send a bug report with crash dialog?