Description: Whenever I try to insert an .mp4 video, either by dragging or using the insert menu, Impress starts to fill the memory, and most of the time gets killed by the OOM killer. If I am able to save before the crash or the Impress stops before getting killed, things turns to normal, and video plays, no problem. I realized that, memory is filled during the thumbnail creation, and stops if the thumbnail is created before the crash. GIFs don't seem to trigger this, but I have not tried another video format. Steps to Reproduce: 1. Insert an mp4 into a slide in Impress. 2. Monitor memory consumption. Actual Results: Memory is filled, system slows to halt, and Impress gets killed by the system. Expected Results: Video inserted successfully without crippling the system. Reproducible: Always User Profile Reset: No Additional Info: System memory: 32 GB
Desktop Environment: KDE Wayland 6.3.4 Integrated GPU: Intel UHD 630 Dedicated GPU: NVIDIA GeForce GTX 1650 Kernel 6.13.8
*** This bug has been marked as a duplicate of bug 116643 ***
(In reply to m_a_riosv from comment #2) > > *** This bug has been marked as a duplicate of bug 116643 *** I don't think this is a duplicate of that report because it is about playing a slide in a Powerpoint file and this is about inserting. I have experienced this same memory leak with KDE UI, but for some reason didn't report it. I am not at my normal workstation, so can't test if it still happens with 25.2. bilaltasdelen: can you try launching with SAL_USE_VCLPLUGIN=gen libreoffice or SAL_USE_VCLPLUGIN=gtk3 libreoffice and see if that makes a difference. You may also run htop in a different terminal, filter by soffice (F4) and manually kill the process (F9, SIGTERM), if you see the memory starting to leak. I do see there is bug 164866 for gtk3.
Created attachment 200216 [details] Terminal output during the bug.
With both SAL_USE_VCLPLUGIN=gen libreoffice and SAL_USE_VCLPLUGIN=gtk3 libreoffice I was able to insert the video and memory consumption was reasonable. Though, with SAL_USE_VCLPLUGIN=gen libreoffice UI was extremely laggy, and SAL_USE_VCLPLUGIN=gtk3 libreoffice froze once when I played an already inserted video (potentially reproducing bug 164866). I should add the current version I am testing is 25.2.2.2. I was observing this behavior for some time, though. Also, in case it is helpful, I attached the errors printed to the console during the video insertion.
Additional info: SAL_USE_VCLPLUGIN=kf5 libreoffice also seems to work, and is currently looking to be the most stable and snappy option among the others for my system. It can be a workaround for this bug.
I can't reproduce on Debian testing when inserting the Big Buck Bunny movie [1]. Do you reproduce with that particular file as well? Otherwise, can you please attach or provide a link to a sample .mp4 file that triggers this? Please also paste the complete version information from "Help" -> "About LibreOffice for more details. Version: 25.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b7e6e0f150a669aa191b16655e6e03d60946c416 CPU threads: 32; OS: Linux 6.12; UI render: default; VCL: qt6 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: CL threaded [1] https://download.blender.org/peach/bigbuckbunny_movies/BigBuckBunny_320x180.mp4
(In reply to Michael Weghorn from comment #7) > I can't reproduce on Debian testing when inserting the Big Buck Bunny movie > [1]. While I can't reproduce with that file with my local development build, I actually can with the Debian packaged LibreOffice version. This might be either fixed in a newer version of LibreOffice or related to something else (e.g. different QtMultiMedia video backends being used.) Version: 25.2.2.2 (X86_64) / LibreOffice Community Build ID: 520(Build:2) CPU threads: 32; OS: Linux 6.12; UI render: default; VCL: kf6 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-GB Debian package version: 4:25.2.2-1 Calc: threaded
I can reproduce with Big Buck Bunny video. Sometimes first insertion works, but second insertion triggers the bug. Requested information: Version: 25.2.2.2 (X86_64) / LibreOffice Community Build ID: 520(Build:2) CPU threads: 12; OS: Linux 6.13; UI render: default; VCL: kf6 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US 25.2.2-1 Calc: CL threaded
(In reply to bilaltasdelen from comment #9) > I can reproduce with Big Buck Bunny video. Sometimes first insertion works, > but second insertion triggers the bug. Thanks. I can indeed reproduce the issue with my local dev build as well when I try inserting a video multiple times. Pending Gerrit change https://gerrit.libreoffice.org/c/core/+/183867 fixes the issue for me with the default ffmpeg QtMultimedia backend. (For QT_MEDIA_BACKEND=gstreamer, the infinite recursion is also fixed with that change, but it crashes later somewhere in low-level GStreamer code, which *might* possibly be a GStreamer or Qt bug, but I didn't investigate further.)
Michael Weghorn committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/697405b533a8ae5b6a8f5bd184b9344a96f71c69 tdf#166055 qt avmedia: Provide media/player size right away It will be available in 25.8.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Pending backport for 25-2: https://gerrit.libreoffice.org/c/core/+/183914
Michael Weghorn committed a patch related to this issue. It has been pushed to "libreoffice-25-2": https://git.libreoffice.org/core/commit/2308a07698660f84e2e11b3fab8cc75550c6798d tdf#166055 qt avmedia: Provide media/player size right away It will be available in 25.2.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.