Bug 493988 - digikam crashes when trying to review some .mov files
Summary: digikam crashes when trying to review some .mov files
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Preview-Video (show other bugs)
Version: 8.4.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-02 19:27 UTC by 31gabig
Modified: 2024-12-21 08:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 8.6.0
Sentry Crash Report:


Attachments
Example .mov file (3.12 MB, video/quicktime)
2024-10-02 19:27 UTC, 31gabig
Details

Note You need to log in before you can comment on or make changes to this bug.
Description 31gabig 2024-10-02 19:27:29 UTC
Created attachment 174331 [details]
Example .mov file

SUMMARY
When trying to preview some of the .mov videos from an iPhone, digikam crashes. VLC or any phone has no problem playing the video.

STEPS TO REPRODUCE
1. Select the problematic video file.
2. Go to the preview.
3. Observe how digikam stops respoding

OBSERVED RESULT
Digikam stops responding and ultimately crashes.

EXPECTED RESULT
The preview to replay the video.

SOFTWARE/OS VERSIONS
Edition	Windows 10 Pro
Version	22H2
Installed on	‎24/‎08/‎2020
OS build	19045.4957
Experience	Windows Feature Experience Pack 1000.19060.1000.0

ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2024-10-02 20:20:50 UTC
Which digiKam version are you using exactly (Qt5 or Qt6)? Which graphics card are you using? I don't have my Windows computer here at the moment, under Linux there are no problems with it crashing. But it doesn't play very well under VLC either, most of the time it freezes and at the end there are graphics errors.
Please test the upcoming digiKam-8.5.0 version from here:

https://files.kde.org/digikam/

Maik
Comment 2 31gabig 2024-10-02 20:33:30 UTC
I am currently using 8.4.0 with Qt6. I tried the 8.5.0 you suggested but the problem persists without change.
More details about my laptop:
Processor: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz   2.30 GHz
Graphics:  Intel(R) HD Graphics 5500
Comment 3 Maik Qualmann 2024-10-03 19:00:06 UTC
The problem depends on the graphics card. I can reproduce the problem on a computer with an embedded Intel graphics card. The video runs well on a laptop with an AMD GPU.
I want to test whether we can change something using environment variables. Otherwise, I would report the problem to Qt.

Maik
Comment 4 Maik Qualmann 2024-11-23 07:42:25 UTC
Git commit cb0bd378009a9793afeb7ac804def1d7ad93942f by Maik Qualmann.
Committed on 23/11/2024 at 07:40.
Pushed by mqualmann into branch 'master'.

add option to disable video hardware acceleration
Related: bug 496484, bug 492922, bug 492060

M  +13   -4    core/app/main/main.cpp
M  +4    -14   core/utilities/setup/misc/systemsettings.cpp
M  +2    -7    core/utilities/setup/misc/systemsettings.h
M  +10   -28   core/utilities/setup/misc/systemsettingswidget.cpp

https://invent.kde.org/graphics/digikam/-/commit/cb0bd378009a9793afeb7ac804def1d7ad93942f
Comment 5 Maik Qualmann 2024-11-29 20:42:26 UTC
With the current pre-release version of digiKam--8.6.0 it is possible to deactivate the hardware acceleration for video in the digiKam settings under Miscellaneous->System (restart digiKam). On my test system with Intel Graphics the sample MOV can then be played from here without crashing. I do not notice any deterioration in performance for other video files on my test system.

https://files.kde.org/digikam/

Maik
Comment 6 caulier.gilles 2024-12-01 08:55:58 UTC
@31gabig

Do you seen the Maik previous comments ?

Gilles Caulier
Comment 7 caulier.gilles 2024-12-02 06:41:24 UTC
Hi,

digiKam 8.5.0. is out with many fixes and improvements.

https://www.digikam.org/news/2024-11-16-8.5.0_release_announcement/

This report still valid with this version?
Thanks in advance

Gilles Caulier
Comment 8 31gabig 2024-12-20 22:03:29 UTC
Sorry for the late reply.

I just checked and the issue persists with the 8.5.0 release. It is though solved by disabling hardware acceleration in the 8.6.0 pre-release as Maik suggested. I checked on my laptop.