| Summary: | Amarok crashes during reprodution | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Joseana <josi.suicide> |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | roger.k.wells |
| Priority: | NOR | ||
| Version: | 2.6.0 | ||
| Target Milestone: | 2.7 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Joseana
2012-06-29 21:42:29 UTC
The problem doesn't appear to be in Amarok but with Qt. What happens if you erase the current.xspf file located in $HOME/.kde4/share/apps/amarok/ ? Created attachment 72408 [details]
New crash information added by DrKonqi
amarok (2.5.0) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2
- What I was doing when the application crashed:
just starting the application via gnome3 desktop
-- Backtrace (Reduced):
#6 0x0000003974c36285 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7 0x0000003974c37b9b in __GI_abort () at abort.c:91
[...]
#9 0x0000003974c7dda6 in malloc_printerr (action=3, str=0x3974d76818 "double free or corruption (!prev)", ptr=<optimized out>) at malloc.c:5021
#10 0x0000003974c7f08e in _int_free (av=0x7f3050000020, p=0x7f3050020a80, have_lock=1) at malloc.c:3942
#11 0x0000003974c81290 in _int_realloc (av=0x7f3050000020, oldp=0x7f3050020a80, oldsize=<optimized out>, nb=1040) at malloc.c:4432
Roger: please do not attach your backtrace here, it is not the same at all. File erased, and the problem continues Is the backtrace the same? Any news on this? Is this still valid for Amarok 2.6? Closing for lack of feedback, please feel free to reopen this report if you can still reproduce it with Amarok 2.6.0 or later The same crash continuous happens. When I try erase the current.xspf file, the same returns when I start a new playlist and the same things occur. 2012/9/14 Myriam Schweingruber <myriam@kde.org> > https://bugs.kde.org/show_bug.cgi?id=302769 > > Myriam Schweingruber <myriam@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|NEEDSINFO |RESOLVED > Resolution|WAITINGFORINFO |INVALID > > --- Comment #7 from Myriam Schweingruber <myriam@kde.org> --- > Closing for lack of feedback, please feel free to reopen this report if > you can > still reproduce it with Amarok 2.6.0 or later > > -- > You are receiving this mail because: > You reported the bug. > Then please provide a new backtrace In other words:erasing the current.xspf fixes the problem, which then returns with a new playlist. Is there something special about your playlist? Where do the tracks come from, how large is it? > > There's not special in my playlist. The tracks are in my hd, and the > problem > occur in the same way with long playlists or just one music. > > Myriam Schweingruber <myriam@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Version|2.5.0 |2.6.0 > Resolution|--- |BACKTRACE > Target Milestone|2.6 |2.7 > > --- Comment #10 from Myriam Schweingruber <myriam@kde.org> --- > In other words:erasing the current.xspf fixes the problem, which then > returns > with a new playlist. Is there something special about your playlist? Where > do > the tracks come from, how large is it? > > -- > You are receiving this mail because: > You reported the bug. > Are the tracks local tracks or are those from a remote share? Still waiting for a new backtrace. The tracks are all local tracks. 2012/10/21 Myriam Schweingruber <myriam@kde.org> > https://bugs.kde.org/show_bug.cgi?id=302769 > > --- Comment #12 from Myriam Schweingruber <myriam@kde.org> --- > Are the tracks local tracks or are those from a remote share? > > Still waiting for a new backtrace. > > -- > You are receiving this mail because: > You reported the bug. > (In reply to comment #9) > Then please provide a new backtrace I asked you in July already, and a month ago: please provide a new backtrace, else I will have to close this report as you don't provide the needed feedback. Closing for lack of feedback, Please feel free to reopen if you can reproduce this and provide a new backtrace, as requested. |