-
-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashes randomly when switching to another song in the playlist if a song's playing #1633
Comments
Need a backtrace of the crash: https://wiki.strawberrymusicplayer.org/wiki/Backtrace |
Hi there! Sorry for my ignorance, it's the first time I'm doing this. I followed the instructions on the wiki but when I typed "bt" (after the app crashed), terminal just says "No stack.". I'm still with the terminal open on the gdb prompt, is there anything else I can do or should've done? |
OK OK so I figure I must install the debug packages, right? Here's what I did: I went to the latest release's page (https://github.com/strawberrymusicplayer/strawberry/releases/tag/1.2.3) and got the debuginfo and debugsource rpms for Leap 15.6 (which I presumed was the meaning of lp156). Then I ran the commands again. For some reason the player took muuuch longer to crash than when I didn't have these packages installed (the previous comment). Then it took like 20 plays for a crash to happen, which was kind of my experience when I wasn't trying to debug it. Now it went on for 10 minutes until it finally crashed. Anyway, here's what I got from the final "bt" command:
Please let me know if there's anything else I could do to help! |
Are you using Leap 15.6 or Tumbleweed? Or are you using the Leap 15.6 package on Tumbleweed? If you are using Leap packages on Tumbleweed, those are not compatible and could cause crashes. Strawberry is in the official repositories, to get debug package you need to add the debug repository. What output do you use in Settings / Backend? And are any of the fading features enabled? |
Aaahh, yes, I'm using Tumbleweed but I didn't know I had to activate a repo, and when I didn't find the package I downloaded Leap's. Sorry! I'll be coming back shortly with an updated "bt" output As for the Settings / Backend, the main config is "Wrapper audio sink for automatically detected audio sink". In the "Options" setting only the first one is marked (something like "Enable volume control"; my language is PT-BR). The buffer settings are 4000, 0,33, and 0,99, which I imagine are defaults cause I didn't mess with it. There's no audio normalisation. |
So here it goes:
gdb told me I was "Missing separate debuginfos", please let me know if there's anything else more specifically that I need to install before providing a good backtrace for this. Thanks for looking into it this soon, btw!! |
When you paste a backtrace you need to use |
The backtrace is missing debug symbols for glib, but a backtrace for this crash isn't too helpful anyway, it just means that an object was deleted before a signal/slot was finished, but it's difficult to know where. Are any of the fading options enabled? I mean these: Can you try disabling those and see if that fixes the crash? |
"The app never crashes if I first pause the song that's playing before starting another one." I came to report this is no longer the case. Just had a crash when the song was paused as well. |
If it helps (if the backtrace hasn't somehow informed this) the new song does start playing for like a quarter of a second before the player crashes I think soon I'll be able to back up the config files and test a fresh run to see if any non-default settings are causing this |
@jonaski I think I found the culprit: moodbars. I backed up the config files/folders (in .cache, .config, .local/state, .local/share) and started the player again. Created a playlist with about 500 songs from the embedded file browser (i.e. didn't even recreate the library). I switched amongst them for like 10 minutes, could not reproduce the bug. So I restored the back up. I found the bug again almost immediately (after switching songs around 10 times). I wanted to back them up again, and this time (from an "empty" install) recreate the library and see if the bug only appeared when the files being played were on the library. Who knows, right, maybe that made a difference. But then I decided to first try playing with configuration. So I disabled the moodbar. I used a ~800-song playlist - one the bug was affecting all these days - and could not reproduce the bug. I turned the moodbar on again. I ran into the bug after around 20-30 switches of songs. I intend to use the player without the moodbar now and report back if the bug turns up again. I don't know if you use the moodbar or what settings you have for it but maybe you can reproduce the bug now. But if you don't if this helps narrow it down in any way, like, providing a better backtrace or something like that, please let me know! |
I can't reproduce this, but I've made some changes to the moodbar that might fix this, please try the latest changes, you can use my repository which has the latest changes from git:
|
I'll try it out! Expect a report back in a day or two |
The bug is still affecting me, unfortunately :/ |
Is it still just crashing when the moodbar is enabled? |
I only used the app with the moodbar enabled, so that I could test the changes. |
Phew, there were a LOT of lines! I used pastebin: https://pastebin.com/uxyu1HQ6 Let me know if you'd rather have me paste it here inside the code tags |
From that backtrace it's looks to be specific to the breeze style. |
Good news! With the fusion style, try as I might, I cannot reproduce the bug. |
Were you able to reproduce it in your setup, with Breeze? |
No I can't reproduce it even when using the Breeze style, but maybe it's only crashing with specific KDE settings. |
In any case, this is probably a KDE breeze style bug |
Should I report it to KDE, then? |
Yes that would be great, I can supply info if they need something more. |
Maybe the crash is specific to Wayland since I can't reproduce it, I use X11 on all my machines. |
Oooh yes, Wayland, you probably stumbled upon something there, that would explain why it only shows up here. Yes, yes, I'll do the reporting there (probably tomorrow or in a couple of days) and mention your offer of more information. In the meantime I'll just disable the moodbar. Thank you so much!! |
Bug reported! https://bugs.kde.org/show_bug.cgi?id=498463 |
So, after using it for a while without the moodbar enabled, the bug struck again. Does that change anything about the current supposition that Breeze on Wayland is at fault? I imagined not, but wanted to check |
I'm also affected by this crashing thing while playing songs in playlists. I'm using Openbox/X. I don't use any moodbar, or fading effect, or any notifications features. Also I use only the Breeze mouse cursor, no Breeze theme/icons. This is what syslog prints when it happens:
|
@morfikov Can you try to get a backtrace please?
|
I'll try it when it occurs again. |
I know how to crash it. Basically I use the @jonaski Is the following info useful?
|
@morfikov |
I've done testing under wayland now and I still cannot reproduce this crash under wayland either, I've switched songs many hundred times. It would be nice to know if you have enabled any additional features in the settings that aren't enabled by default, if possible rename/bacup strawberry.conf to try with the default configuration and check if you can still reproduce the crash. |
@jonaski Actually I did it, I mean I installed all the necessary debug packages:
And the result is posted in my previous message. What could hide them? Some kernel/sysctl setting? |
@jonaski I think I got it. I hope this has some useful info.
|
@morfikov That crash looks related to the tagreader, have you enabled writing playcounts to file? |
Yes, saving playcounts and ratings to tags are set. I disabled saving playcounts to tags for now. Tried to crash but so far I was unable to do it I also tried to change ratings and also was able to crash the app. So something is wrong with the two options. |
Makes sure TagReaderReplyPtr is not deleted too early. Partial fix for #1633
@jonaski , I think it's ok now. I tried to crash the app with the two options enabled, but it's working well. I'll test it more and get back to this with results by the end of the week. |
@jonaski I also have saving playcounts and ratings to song tags enabled, should this fix work for me as well? |
@petersonespacoporto Yes, please test, the changes should be published to the OBS repository so just do zypper dup to update, if it works please close the KDE bug. |
Describe the bug
Strawberry crashes randomly if there's a song playing and I start playing another song in the same playlist.
To Reproduce
Have multiple songs in a playlist; start playing one; switch to a different one while the first is still playing. Sometimes the app will just crash. This has happened to me by either double-clicking it or pressing 'Enter' when the new song's selected.
Expected behavior
The app should not crash.
System Information:
Operating System: openSUSE Tumbleweed 20241226
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.6-1-default (64-bit)
Graphics Platform: Wayland
Processors: 6 × AMD Ryzen 5 3500X 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: NV106
Additional context
The app never crashes if I first pause the song that's playing before starting another one.
I have run the app in the terminal to see what I could get the moment it crashes but all it gives me is a standard segfault: "Falha de segmentação (imagem do núcleo gravada)" (my system's in Portuguese, in English I'm guessing that would be "Segmentation fault (core image recorded)"). Don't know if that helps or not, but I'm willing to provide any further information needed to fix this :)
The text was updated successfully, but these errors were encountered: