Bug 464187 - DigiKam crashes while examining videos and gifs
Summary: DigiKam crashes while examining videos and gifs
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Preview-Video (show other bugs)
Version: 8.0.0
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2023-01-12 10:32 UTC by Fritigern
Modified: 2023-10-18 09:54 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 8.2.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fritigern 2023-01-12 10:32:23 UTC
Application: digikam (8.0.0-git)

Qt Version: 5.15.6
Frameworks Version: 5.98.0
Operating System: Linux 5.19.0-28-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.10
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
DigiKam crashes consistently while viewing videos (mpg, mp4, webm, etc) and gifs.
This is a little frustrating because DigiKam used to handle these files without issue in the past.

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Bus error

[KCrash Handler]
#4  0x00007fc97408f079 in avcodec_close () at /lib/x86_64-linux-gnu/libavcodec.so.59
#5  0x00007fc974623b8d in avcodec_free_context () at /lib/x86_64-linux-gnu/libavcodec.so.59
#6  0x00007fc97969b5ba in QtAV::AVDecoder::setCodecContext(void*) () at /usr/lib/digikam/libdigikamcore.so.8.0.0
#7  0x00007fc97969b72d in QtAV::AVDecoder::~AVDecoder() () at /usr/lib/digikam/libdigikamcore.so.8.0.0
#8  0x00007fc9796a1d8b in  () at /usr/lib/digikam/libdigikamcore.so.8.0.0
#9  0x00007fc97962e641 in  () at /usr/lib/digikam/libdigikamcore.so.8.0.0
#10 0x00007fc979624e2c in QtAV::AVPlayerCore::playInternal() () at /usr/lib/digikam/libdigikamcore.so.8.0.0
#11 0x00007fc9778f372c in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007fc9778e7b30 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007fc97856bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007fc9778bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007fc9778bdeb1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007fc977915427 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007fc968d224f9 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fc968d77228 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fc968d1fcb0 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fc977914aea in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007fc9778b97cb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007fc9778c1c2a in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x0000560e52c1f9a1 in  ()
#24 0x00007fc976e23510 in __libc_start_call_main (main=main@entry=0x560e52c1e800, argc=argc@entry=1, argv=argv@entry=0x7ffcfdd8eec8) at ../sysdeps/nptl/libc_start_call_main.h:58
#25 0x00007fc976e235c9 in __libc_start_main_impl (main=0x560e52c1e800, argc=1, argv=0x7ffcfdd8eec8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffcfdd8eeb8) at ../csu/libc-start.c:381
#26 0x0000560e52c204d5 in  ()
[Inferior 1 (process 468464) detached]

Reported using DrKonqi
Comment 1 Maik Qualmann 2023-01-12 11:28:34 UTC
I have no problems with video files here. Can you please test it with our digiKam-8.0.0-Beta1 AppImage from here:

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

Maik
Comment 2 caulier.gilles 2023-01-12 11:42:35 UTC
Check also the Setup/Video page to see if a back-end is selected, especially the ffmpeg.

Gilles Caulier
Comment 3 Fritigern 2023-01-13 09:15:13 UTC
(In reply to Maik Qualmann from comment #1)
> I have no problems with video files here. Can you please test it with our
> digiKam-8.0.0-Beta1 AppImage from here:
> 
> https://files.kde.org/digikam/unstable/
> 
> Maik

The appimage works fine, it's just that in the "installed" version 8.0.0 (From the Kubuntu Universe repos) everything messes up.
It is my understanding that an appimage containes all the dependencies and stuff, and this is pretty much guaranteed to work well.

I noticed that the appimage utillizes avcodec 58.134.100 while Kubuntu 22.10 does not have that package, instead it uses avcodec 59.37.100 without the option to downgrade to avcodec58 so now I am wondering if this is the cause of the issue.

About the GIFs, I ran DigiKam in a terminal, clicked an animated GIF which was previously known to work in DigiKam as well as in the appimage and in the "installed" version it shoed a single still in the GUI and on the terminal it showed:

digikam.qtav.warn: no frame could be decompressed: Success 48974 / 48974
digikam.qtav.warn: invalid video frame from decoder. undecoded data size: 48974
digikam.qtav.warn: Invalid plane! Valid range is [0, 0)
digikam.qtav.warn: Invalid plane! Valid range is [0, 0)
digikam.qtav.warn: Invalid plane! Valid range is [0, 0)
digikam.qtav.warn: Can not copy codec properties when it's open
Comment 4 Fritigern 2023-01-13 09:15:56 UTC
(In reply to caulier.gilles from comment #2)
> Check also the Setup/Video page to see if a back-end is selected, especially
> the ffmpeg.
> 
> Gilles Caulier

FFMpeg is selected. Version 59.134.100
Comment 5 caulier.gilles 2023-01-13 09:27:43 UTC
Yes problems with ffmpeg 5 are knows: https://bugs.kde.org/show_bug.cgi?id=448681

This is why we use ffmpeg 4 in the bundles that we provides.

Gilles Caulier
Comment 6 Maik Qualmann 2023-01-15 12:02:06 UTC
*** Bug 464319 has been marked as a duplicate of this bug. ***
Comment 7 caulier.gilles 2023-05-06 08:49:54 UTC
@Fritigern

digiKam 8.0.0 is out. Problem still reproducible with this release ?

Gilles Caulier
Comment 8 Maik Qualmann 2023-06-02 11:12:38 UTC

*** This bug has been marked as a duplicate of bug 468480 ***
Comment 9 caulier.gilles 2023-10-18 09:54:39 UTC
Fixed with  468480