[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amarok-bugs-dist
Subject:    [amarok] [Bug 359382] New: Clicking Merged View causes apparent hang (100% CPU use)
From:       Bernd Wechner via KDE Bugzilla <bugzilla_noreply () kde ! org>
Date:       2016-02-14 10:19:33
Message-ID: bug-359382-71684 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=359382

            Bug ID: 359382
           Summary: Clicking Merged View causes apparent hang (100% CPU
                    use)
           Product: amarok
           Version: 2.8.0
          Platform: Mint (Ubuntu based)
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: Collection Browser
          Assignee: amarok-bugs-dist@kde.org
          Reporter: bernd.wechner@gmail.com

Merged View is poorly documented. I don't know what it does, or is intended to
do.

The KDE Help Center simply says: Displays the podcasts in a merged or unmerged
view.

Which tells me little.

So I clicked it to see what happens. And it kills the Amarok UI. Linux still
responds, even the menu on the Amarok system tray icon still displays, but
Amarok responds to nothing.

It sits there with 100% CPU usage (I am on a twin core i5 machine) and seems to
do so beyond my patience limits so I kill it (with -9) and it doesn't respond
to polite request. I restart it and all is good, but if I click the Merged View
button again - go to beginning of this report.

I have repeated this a third time juts for fun ;-).

Now for context I have Local Collection selected when do this and it is hosted
on a QNAP NAS and does have over 200,000 tracks in it. 

Still,  the behaviour is puzzling given a lack of clarity as to what this
button is actually doing.

I'd call this a bug. You may disagree, in which case triage appropriately of
course. But at very least I would expect:

1) Better documentation as to what Merged View actually is
2) If the operation is going to take so long a clear progress indicator with
cancel option.

Lacking either doesn't meet with my expectations as a user I admit.

Reproducible: Always

Steps to Reproduce:
1. Start Amarok, with a local collection hosted on a network accessed NAS
mounted on the local Linux file system, that contains a large number of tracks
(> 200,000)
2. On the Media Sources pane navigate to Local Collection
3. Click the Merged View button

Actual Results:  
Amarok UI hangs.
Amarok is using 100% of CPU (presumably 1 core of the 2 cores on my box as
Linux responds still)


Expected Results:  
Amarok continues to respond
If it's an extremely expensive operation: a progress indicator with a cancel
option
Documentation that describes what to expect (what the heck is Merged View?)

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Amarok-bugs-dist mailing list
Amarok-bugs-dist@kde.org
https://mail.kde.org/mailman/listinfo/amarok-bugs-dist

[prev in list] [next in list] [prev in thread] [next in thread]