Bug 290835

Summary: Amarok hangs when "watch folder for changes" is initiated
Product: [Applications] amarok Reporter: bill p. (aka google01103) <dweeble01103>
Component: Collections/LocalAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED DUPLICATE    
Severity: normal CC: igor.poboiko, ralf-engels
Priority: NOR    
Version: 2.5-git   
Target Milestone: 2.6   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: backtrace

Description bill p. (aka google01103) 2012-01-06 22:59:32 UTC
Version:           2.5-git (using Devel) 
OS:                Linux

Running latest KDE 4.8 (4.8 RC2 (4.7.97) "release 1") and Amarok from 1/5 (with
applet toolbar fix). Amarok was uninstalled and I did a fresh git clone
ran with --debug, hang is difficult to kill had to force kill in
ksysguard

when open and playing (started with --debug) it hangs at:
amarok: BEGIN: void ScanManager::checkScannerVersion() 

latest hang was after:
scan  END__: virtual
void DirWatchJob::run() [Took: 1.4s])

notes:
- when "watch folder for changes" is disabled all appears to function fine
- manually invoking "update collection" causes no problems

Reproducible: Always

Steps to Reproduce:
open Amarok 

Actual Results:  
wait for Amarok to initiate watch folder process

Expected Results:  
Amarok does not hang
Comment 1 Igor Poboiko 2012-01-29 00:39:34 UTC
Can reproduce this with 2.5.0 installed from Gentoo Portage with KDE SC 4.8.0.
This bug was critical for me. Amarok was totally unusable because it hanged every time few seconds after I start it. 
All the symptoms are the same. After disabling "watching folder for changes", Amarok doesn't hang anymore.
Comment 2 Myriam Schweingruber 2012-01-29 17:51:08 UTC
I can't reproduce this with current 2.5-git, KDE 4.8 on Kubuntu 11.10, maybe there is some specifics of your system causing that? Are your files on a local partition? Are you suing KySQL embedded or an external MySQL server?
Comment 3 bill p. (aka google01103) 2012-01-29 22:47:31 UTC
afaik my install (self compiled) is standard issue, I use the std db as configured by Amarok with all my files on my home folder. I even removed all config files and app folders other than mysqle and albumcovers to no avail.
Comment 4 Igor Poboiko 2012-01-29 22:49:27 UTC
Well, I can't see nothing special in my system. All my files are on a local ntfs (ntfs-3g) partition. And I use MySQL embedded. I'm going to try the version from git and see it helps.
I've also tried removing all the config files (~/.kde4/share/apps/amarok and ~/.kde4/config/amarok*) and it didn't help.
And this bug seems to be a regression. I didn't have it when was using Amarok 2.3 version (or like that; I cannot remember the first version it appeared). But it may also be because of some file appeared in my collection last time. Going to do some experiments (with collection and maybe with previous amarok versions) and see where's the problem.
Comment 5 Igor Poboiko 2012-01-29 23:32:24 UTC
Created attachment 68319 [details]
backtrace

Still reproducable with latest git.
I've run amarok in gdb, interrupted it by pressing Ctrl+C and used "thread apply all bt" to get attached backtrace.
Latest few lines from debug log:

amarok: BEGIN: virtual void ScannerJob::run() 
amarok:   BEGIN: virtual void DirWatchJob::run() 
amarok:     END__: void ScanManager::checkForDirectoryChanges() [Took: 0s] 
amarok:     [ScanManager] ScannerJob: got count: 642 
amarok:     BEGIN: virtual void SqlScanResultProcessor::commit() 
amarok:     END__: virtual void SqlScanResultProcessor::commit() [Took: 0.22s] 
amarok:     [ScanManager] ScannerJob finished 
amarok:   END__: virtual void ScannerJob::run() [Took: 1.6s]
Comment 6 Myriam Schweingruber 2012-01-30 07:12:49 UTC

*** This bug has been marked as a duplicate of bug 281312 ***