Saturday 13 November 2010, Kevin Funk :
> Hey guys,
>
> Mikko C. sent me some weird backtrace where an assert in QString is
> triggered.
>
> Assert is triggered here:
> #11 0x7f9651d39f5b in replaceArgEscapes (s=,
> d=, field_width=, arg= optimized out>, larg=, fillChar=...) at
> tools/qstrin
Hello,
Below are my observations too, just to see if other users' compare.
On Sat, Nov 13, 2010 at 4:06 AM, Mikko C. wrote:
> Hi,
> I found some time to run some tests with the new scanner.
>
> Amarok from git master of today:
> Full rescan with the collection already being present on the extern
Just happened to me too. I had just switched to Gstreamer backend,
just for kicks. I ended up turning off Amarok because it was
persistant, large and annoying. Freshly built from git today.
Valorie
On Fri, Nov 12, 2010 at 5:36 AM, Leo Franchi wrote:
> On Friday, November 12, 2010 08:40:41 AM Bar
Follow up.
-- Weitergeleitete Nachricht --
Betreff: Fwd: crash in Debug::dbgstream ?
Datum: Freitag 12 November 2010, 22:07:17
Von: "Mikko C."
An: k...@electrostorm.net
Hi,
I just got the same crash again, during another full rescan.
amarok SRP::commitAlbum on "Hail To The
Hey guys,
Mikko C. sent me some weird backtrace where an assert in QString is triggered.
Assert is triggered here:
#11 0x7f9651d39f5b in replaceArgEscapes (s=,
d=, field_width=, arg=, larg=, fillChar=...) at
tools/qstring.cpp:6434
Relevant debug() call in Amarok is here:
#16 0x7f961524
Hi,
I found some time to run some tests with the new scanner.
Amarok from git master of today:
Full rescan with the collection already being present on the external
MySQL database.
- 11:30 mins for the first scanning part (up to 50% in the progress bar)
- 2:50 mins for the last part (remaining 5
