Bug 449692 - Kdenlive crash when opening video with OpenGL enabled
Summary: Kdenlive crash when opening video with OpenGL enabled
Status: REPORTED
Alias: None
Product: kdenlive
Classification: Applications
Component: Video Display & Export (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-06 10:55 UTC by Andreas
Modified: 2022-02-06 12:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Kdenlive crash report (31.64 KB, text/vnd.kde.kcrash-report)
2022-02-06 10:55 UTC, Andreas
Details
Terminal output (7.65 KB, text/plain)
2022-02-06 10:58 UTC, Andreas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas 2022-02-06 10:55:23 UTC
Created attachment 146335 [details]
Kdenlive crash report

SUMMARY
***
When OpenGL is activated and trying to open a video, Kdenlive crashes.
If I open a video with OpenGL disabled and save the project, then turn on openGL and load the saved project, everything works.
Without OpenGL, 4K60fps playback on Timeline is very slow.
The error occurs on Kdenlive 21.12.2 and older versions. I use openSUSE Tumbleweed and installed Kdenlive from the repositories, also tried the Flatpak version, but the result is the same.
It also doesn't matter if I'm using an Intel or NVIDIA GPU.
***


STEPS TO REPRODUCE
1. Enable OpenGL in playback settings
2. Open 4K60/50fps video


OBSERVED RESULT
kdenlive crashes

EXPECTED RESULT
Kdenlive won't crash

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20220204
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.16.4-1-default (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION
Processors: 12 × Intel® Xeon® E-2186M CPU @ 2.90GHz
Memory: 125.5 GiB of RAM
Graphics Processor: Quadro P3200/PCIe/SSE2
Comment 1 Andreas 2022-02-06 10:58:09 UTC
Created attachment 146337 [details]
Terminal output
Comment 2 Andreas 2022-02-06 12:27:04 UTC
I think it's the same issue
https://bugs.kde.org/show_bug.cgi?id=442880