/usr/lib64/libgstreamer-0.10.so.0.30.0

Your gstreamer version is from 2010.... i'd start about there.

Most memory warnings seem t stem from QTJSC::Heap - equally old Qt?

Cheers,
Thomas

On Sonntag, 17. Februar 2013 17:47:22 CEST, Alexander Puchmayr wrote:
Hi there,

I've been very busy with other things last weeks, but finally I managed to upgrade my gentoo system to kde-4.9.5 and amarok-2.7.0, and the relevant packages compiled with USE="debug" and CXXFLAGS="-march=amdfam10 -O2 -ggdb" and FEATURES=nostrip to prevent debugging symbols from being removed before the final install.

There is still no improvement, i.e. amarok still crashes after a few minutes. The crash log from

gdb amarok
(gdb) run -d --nofork

shows a SIGSEGV at different locations and different threads each time, which indicates that the SIGSEGV is only a secondary symptom, and the actual bug is somewhere else. I installed valgrind and ran amarok with it, the result is appended to this mail.

Greetings
        Alex



Am Sonntag, 6. Januar 2013, 14:24:23 schrieb Myriam Schweingruber:
Hi Alexander,

On Sun, Jan 6, 2013 at 2:16 PM, Alexander Puchmayr

<alexander.puchm...@linznet.at> wrote:
Hi Myriam,

Thank you for the quick reply!

Please see the attached output (I'm afraid it will be of no much use as
there are too much '??' instead of useful symbols :-( )


...

Well, of course you will need to have the DEBUG flags enabled for these....

But since you are using Gentoo, could you test the latest git version
of Amarok? For us version 2.6 is rather old now and we have added so
many fixes since August (over 300 closed bug reports) and are about to
release Amarok 2.7 that it would make more sense to test with a more
recent installation.


Regards, Myriam



_______________________________________________
Amarok mailing list
Amarok@kde.org
https://mail.kde.org/mailman/listinfo/amarok



_______________________________________________
Amarok mailing list
Amarok@kde.org
https://mail.kde.org/mailman/listinfo/amarok

Reply via email to