Bug 499342 - Holding the cursor on the end of any video's progress bar causes Haruna to repeat the video hundred of times per second, causing the app to crash
Summary: Holding the cursor on the end of any video's progress bar causes Haruna to re...
Status: RESOLVED LATER
Alias: None
Product: Haruna
Classification: Applications
Component: generic (show other bugs)
Version: 1.3.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Fernando M. Muniz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-30 19:39 UTC by Fernando M. Muniz
Modified: 2025-02-15 12:40 UTC (History)
2 users (show)

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


Attachments
This doesn't happen with small files. (2.94 MB, video/x-matroska)
2025-01-30 19:39 UTC, Fernando M. Muniz
Details
Another video. (3.87 MB, video/x-matroska)
2025-02-09 11:20 UTC, Fernando M. Muniz
Details
It crashes with light Short videos. (2.73 MB, video/x-matroska)
2025-02-09 11:54 UTC, Fernando M. Muniz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Fernando M. Muniz 2025-01-30 19:39:30 UTC
Created attachment 177835 [details]
This doesn't happen with small files.

When having a heavy 4K/8K video playing, then dragging the progress bar into the last frame of the video; Haruna crashes.
Comment 1 John Kizer 2025-02-05 20:18:52 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!
Comment 2 Fernando M. Muniz 2025-02-05 22:17:48 UTC
I've used journalctl -f then opened a heavy video and kept dragging around the end of the progress bar until it crashed.

[tuti@archlinux ~]$ journalctl -f
fev 05 19:07:55 archlinux systemd[845]: Started Haruna - Media Player.
fev 05 19:07:55 archlinux systemd[845]: Started app-flatpak-org.kde.haruna-21224.scope.
fev 05 19:07:55 archlinux xdg-desktop-portal-kde[1137]: xdp-kde-settings: Key  "menuFont"  doesn't exist
fev 05 19:07:55 archlinux xdg-desktop-portal-kde[1137]: xdp-kde-settings: Key  "font"  doesn't exist
fev 05 19:07:55 archlinux xdg-desktop-portal-kde[1137]: xdp-kde-settings: Key  "activeFont"  doesn't exist
fev 05 19:07:55 archlinux xdg-desktop-portal-kde[1137]: xdp-kde-settings: Key  "toolBarFont"  doesn't exist
fev 05 19:07:55 archlinux xdg-desktop-portal-kde[1137]: xdp-kde-settings: Key  "smallestReadableFont"  doesn't exist
fev 05 19:07:57 archlinux systemd[845]: app-flatpak-org.kde.haruna-21224.scope: Consumed 3.522s CPU time, 1G memory peak.
fev 05 19:08:00 archlinux systemd[845]: Started Konsole - Terminal.
fev 05 19:08:00 archlinux systemd[845]: Started app-org.kde.konsole-21307.scope.
fev 05 19:08:18 archlinux systemd[845]: Started Haruna - Media Player.
fev 05 19:08:18 archlinux systemd[845]: Started app-flatpak-org.kde.haruna-21340.scope.
fev 05 19:08:18 archlinux xdg-desktop-portal-kde[1137]: xdp-kde-settings: Key  "menuFont"  doesn't exist
fev 05 19:08:18 archlinux xdg-desktop-portal-kde[1137]: xdp-kde-settings: Key  "font"  doesn't exist
fev 05 19:08:18 archlinux xdg-desktop-portal-kde[1137]: xdp-kde-settings: Key  "activeFont"  doesn't exist
fev 05 19:08:18 archlinux xdg-desktop-portal-kde[1137]: xdp-kde-settings: Key  "toolBarFont"  doesn't exist
fev 05 19:08:18 archlinux xdg-desktop-portal-kde[1137]: xdp-kde-settings: Key  "smallestReadableFont"  doesn't exist
fev 05 19:08:32 archlinux kernel: QSGRenderThread[21393]: segfault at 0 ip 00007b77ae300f11 sp 00007b77d91f0250 error 4 in iHD_drv_video.so[b00f11,7b77ad96f000+a8f000] likely on CPU 3 (core 3, socket 0)
fev 05 19:08:32 archlinux kernel: Code: 55 41 54 49 89 d4 53 89 f3 48 83 ec 28 48 89 45 b8 e8 73 f4 66 ff 85 c0 0f 85 61 cb 69 ff 49 8b 47 10 41 8b 7f 18 45 8b 6f 1c <8b> 00 89 7d c0 0f b7 fb 89 7d c4 89 45 c8 44 39 e8 0f 84 5a 01 00
fev 05 19:08:32 archlinux systemd-coredump[21416]: Process 21353 (haruna) of user 1000 terminated abnormally with signal 11/SEGV, processing...
fev 05 19:08:32 archlinux systemd[1]: Started Process Core Dump (PID 21416/UID 0).
fev 05 19:08:32 archlinux systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
fev 05 19:08:33 archlinux systemd-coredump[21417]: [🡕] Process 21353 (haruna) of user 1000 dumped core.
                                                   
                                                   Stack trace of thread 41:
                                                   #0  0x00007b77ae300f11 n/a (n/a + 0x0)
                                                   #1  0x00007b77ade9622a n/a (n/a + 0x0)
                                                   #2  0x00007b77adc03fe3 n/a (n/a + 0x0)
                                                   #3  0x00007b77adbe2ad6 n/a (n/a + 0x0)
                                                   #4  0x00007b77adbebf90 n/a (n/a + 0x0)
                                                   #5  0x00007b78267d957c n/a (n/a + 0x0)
                                                   #6  0x00007b7823588a5d n/a (n/a + 0x0)
                                                   #7  0x00007b7823518528 n/a (n/a + 0x0)
                                                   #8  0x00007b7823524aaf n/a (n/a + 0x0)
                                                   #9  0x00007b7823528f3b n/a (n/a + 0x0)
                                                   #10 0x00007b782352c7af n/a (n/a + 0x0)
                                                   #11 0x00007b7823519e36 n/a (n/a + 0x0)
                                                   #12 0x00007b7823536fb9 n/a (n/a + 0x0)
                                                   #13 0x00007b782a2576be n/a (n/a + 0x0)
                                                   #14 0x00007b7826507d24 n/a (n/a + 0x0)
                                                   #15 0x00007b7824404360 n/a (n/a + 0x0)
                                                   #16 0x00007b78262df476 n/a (n/a + 0x0)
                                                   #17 0x00007b7826510aed n/a (n/a + 0x0)
                                                   #18 0x00007b7826512003 n/a (n/a + 0x0)
                                                   #19 0x00007b782456862f n/a (n/a + 0x0)
                                                   #20 0x00007b7823c98e0e n/a (n/a + 0x0)
                                                   #21 0x00007b7823d1d7d4 n/a (n/a + 0x0)
                                                   ELF object binary architecture: AMD x86-64
fev 05 19:08:33 archlinux systemd[1]: systemd-coredump@1-21416-0.service: Deactivated successfully.
fev 05 19:08:33 archlinux systemd[1]: systemd-coredump@1-21416-0.service: Consumed 674ms CPU time, 460.9M memory peak.
fev 05 19:08:33 archlinux systemd[845]: app-org.kde.haruna@1ebe687c96e542f0b93794616410d7b5.service: Main process exited, code=exited, status=139/n/a
fev 05 19:08:33 archlinux systemd[845]: app-org.kde.haruna@1ebe687c96e542f0b93794616410d7b5.service: Failed with result 'exit-code'.
fev 05 19:08:33 archlinux systemd[845]: app-flatpak-org.kde.haruna-21340.scope: Consumed 6.268s CPU time, 1G memory peak.
fev 05 19:08:33 archlinux drkonqi-coredump-processor[21418]: "/app/bin/haruna" 21353 "/var/lib/systemd/coredump/core.haruna.1000.d3525b1bb7194e329e8c20fe8c5c8ac4.21353.1738793312000000.zst"
fev 05 19:08:33 archlinux systemd[845]: Started Launch DrKonqi for a systemd-coredump crash (PID 21418/UID 0).
fev 05 19:08:33 archlinux systemd[1]: drkonqi-coredump-processor@1-21416-0.service: Deactivated successfully.
fev 05 19:08:33 archlinux drkonqi-coredump-launcher[21429]: Unable to find file for pid 21353 expected at "kcrash-metadata/haruna.d3525b1bb7194e329e8c20fe8c5c8ac4.21353.ini"
fev 05 19:08:33 archlinux drkonqi-coredump-launcher[21429]: Nothing handled the dump :O
Comment 3 george fb 2025-02-07 19:24:06 UTC
First, stop deleting the template and provide the info requested when reporting bugs.
Provide sample file.

Also read https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 4 Fernando M. Muniz 2025-02-07 20:17:03 UTC
(In reply to george fb from comment #3)
> First, stop deleting the template and provide the info requested when
> reporting bugs.
> Provide sample file.
> 
> Also read
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports

I downloaded this video with yt-dlp
https://www.youtube.com/watch?v=LXb3EKWsInQ

Then did exactly as the Description did.
Comment 5 Fernando M. Muniz 2025-02-07 20:19:03 UTC
Or rather, I did exactly as shown in the attached video and explained in the Description
Comment 6 george fb 2025-02-08 18:34:13 UTC
I can't reproduce.
Comment 7 Fernando M. Muniz 2025-02-09 11:20:45 UTC
Created attachment 178091 [details]
Another video.
Comment 8 george fb 2025-02-09 11:54:13 UTC
There's the point posting videos showing the bug. 
What you need to post is a backtrace with debug symbols installed, as described in the page https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 9 Fernando M. Muniz 2025-02-09 11:54:34 UTC
Created attachment 178092 [details]
It crashes with light Short videos.

Seems like the real issue is that Haruna panics when holding the end of the progress bar because it will replay the video multiple times under per second, which crashes the player.

https://www.youtube.com/shorts/zT0SRSh0JIo

The only solution seems to be not allowing videos to replay if the user is holding the progress bar, otherwise it will replay until it crashes or hard resets the video.
Comment 10 george fb 2025-02-09 11:58:14 UTC
For the last time, you need to provide a backtrace while you have debug symbols installed.
And don't change the status however you see fit.
Comment 11 Fernando M. Muniz 2025-02-15 12:40:43 UTC
I'm marking this for later, since I think these crashes are just a symptom of a badly designed area.