| Summary: | [Windows, OSX] "Configure Amarok..." causes temporary UI freeze | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Diego <diego.ml> |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | apoorvkhatreja, casper.vandonderen, dmeltzer.devel, illogical1, lfranchi, ps_ml, vonreth, x.para, yulidanroni |
| Priority: | HI | ||
| Version First Reported In: | 2.3-GIT | ||
| Target Milestone: | 2.4.0 | ||
| Platform: | unspecified | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Screenshot of the "Configure Amarok..." UI during the freeze
Screenshot of the "Configure Amarok..." UI after the freeze Amarok debug output on Windows. Debug Dump file Crash file Amarok debug output on Windows after little progresses. Amarok 2.2 debug output on Windows. |
||
|
Description
Diego
2009-02-04 15:07:21 UTC
Mmm... looking at the screenshots I just grabbed I probably got why the "General" option doesn't occupy the whole width: the space on its right is reserved for the scrollbar, which hasn't already been draw. I don't think the screenshots will be very useful, but I'll post them anyway, one can never know. Created attachment 30956 [details]
Screenshot of the "Configure Amarok..." UI during the freeze
This is a screenshot of the "Configure Amarok..." UI during the freeze.
Sorry for the Windows menu intrusion. ^_^
Created attachment 30957 [details]
Screenshot of the "Configure Amarok..." UI after the freeze
This is a screenshot of the normal UI (after the freeze).
*** Bug 175763 has been marked as a duplicate of this bug. *** This appears to happen on OSX too. We've had a bug report about that. Not sure what happened to it. @Diego: Could you please start Amarok from a shell terminal with "amarok --debug", and then attach the full output here (including when you open the settings dialog)? @SaroEngels, @Orville: Any ideas? @Mark: I'm sorry, Windows Command Prompt seems to ignore command line arguments. amarok --debug just starts amarok, but no output appears... I tried also with Console2 which seems a bit more "modern" than cmd.exe but had the same results. @Diego: I think there is some trick for achieving it, but sadly I don't know/remember it.. :( Maybe SaroEngels knows, we'll see. Yes, to collect the debug output, get yourself a copy of debugview from sysinternals.com (http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx). Then start dbgview.exe and from there you can get the output of 'amarok --debug'. The problem is that stdout/stderr are not redirected to the console on windows, thus you can't get this in a simple way. About the bug: I am not sure I have seen this bug yet, I will look later today if my old version already has it and then I'll try to update. @Saro: I read something about it here: http://techbase.kde.org/Development/Tutorials/Debugging/Debugging_on_MS_Windows and here: http://amarok.kde.org/wiki/Download:Windows but it wasn't clear to me what to do exactly. Thanks for the reply, log incoming! ;) Created attachment 30994 [details]
Amarok debug output on Windows.
The freeze is beetween lines #178 and #179:
00000178 61.22303772 [524] amarok: END__: ServiceConfig::hasChanged - Took 0s
00000179 72.34948730 [524] amarok: BEGIN: ScanManager::startIncrementalScan
Same problem here. Annoying. Created attachment 32288 [details]
Debug
@x.para: Uhm.. could you please attach that in _plain_ normal text? It seems you attached a MS Word document... we've been wondering if it's Klingon or so ;) Created attachment 32293 [details]
Dump file
This time again not sure if this helps as this seems to be hexa file, but I don't know better option how to provide dump log. WXP does not allow me to ctrl+c its output.
@x.para: The normal way to get debug output from Amarok 2 is to start it from a shell (PowerShell or so on Windows), and starting it with "amarok --debug". Then just attach that text output here. Wish to help, but no debugs commands received using powershell or native cmd :( PS C:\> cd 'C:\Program Files\KDE\bin' PS C:\Program Files\KDE\bin> .\amarok.exe --debug PS C:\Program Files\KDE\bin> You need to install debugview: http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx Created attachment 32298 [details]
Crash file
@x.para: Thanks, this latest debug output is much better :) Still, I can't see any trace in it of the Configure dialog code. Did you actually open it while you were recording this output? Fixing this bug has a high priority to me, so I request everyone here to provide as much information as possible. *** Bug 170195 has been marked as a duplicate of this bug. *** Well first I ran debugview and than Amarok, so it should be pretty complete. But if there is other better way, let me know. Ok, I think we really need to make some progress with this report. Isn't anyone able to figure this out? We can hardly release 2.1 when it takes 10 seconds to open the config dialog. With the help of DEBUG_BLOCK and friends it should be possible to find the culprit. I would do it if I had Amarok running on OSX or Windows - but on Linux, I cannot reproduce the problem at all. Another approach: Disabling config pages one by one, until the problematic one is found. If I should try to make a blind guess of what config page (if one of them is the responsible) is causing the freeze I'd go for the "Collection" page. This is because the freeze happens after the "General" page is loaded, and just before the "Collection" page is loaded. Please check it it is still happening with the packages from this server: http://mafia-server.net/amarok-nightly The issue is still there but there are some progresses: now the whole config interface gets drawn before the UI freeze, but then again you are not able to click anywhere for a couple of seconds (while the music continues to play normally). No relevant output on the debug during the freeze. Created attachment 34018 [details]
Amarok debug output on Windows after little progresses.
This is the log file with the 26/05/09 build.
Any news on this? Casper, could you look at this by any chance? This seems like a major problem. Maybe add some debug output to the config dialog code? Thanks :) Does not happen on my setup: KDE 4.3.65 MSVC2008 with Vista Platform SDK Amarok 2.2 Git Maybe this has got fixed "for free"... I'll double check when packages of 2.2 are out. However this happened also to our Mac friends: is it "automagically" fixed for you too? (In reply to comment #30) > Maybe this has got fixed "for free"... I'll double check when packages of 2.2 > are out. > However this happened also to our Mac friends: is it "automagically" fixed for > you too? Yep. Good to go. Great, closing then :) Sorry, it's not fixed here. :( Amarok 2.2 vc-90 nightly builds (mafia-server) 18/09/09 with KDE 4.3.0 (mafia-server), Windows XP SP3. Could it be something fixed in 4.4 trunk and not in 4.3? Log incoming. Created attachment 37039 [details]
Amarok 2.2 debug output on Windows.
The freeze is between second 32 and 40 in the log.
So, it's almost November 2009 now. It appears that we don't have a single competent Windows/Mac developer who can solve this issue. Sad state of affairs. For those of you who are actually affected by this issue: Please help us get more Windows/Mac developers! Just spread the word, blog about it, etc. Every bit helps. As mentioned by Casper in comment #29 he is running trunk, so maybe this is fixed in 4.4svn or even 4.3.x with x >= 1. Unfortunately the nightly builds are against KDE 4.3.0... I'm asking in the forums for others to report their experience: http://forum.kde.org/viewtopic.php?f=59&t=83278 Apart from the default Phonon backend (DS = crap, VLC = good) this is to me the latest showstopper of Amarok for Windows. It's not that nasty (it doesn't crash anything) but it's not pleasant at all... It persists in today's nightly together with KDE 4.3.2, so if a fix is present it's in KDE 4.4. Maybe it's Windows version dependant, who knows... Changing version and target. Since most people actually use the nightly builds, this makes more sense. removing keyword, pointless to push back a release if there are not enough people working on it KDE 4.5.4. Amarok 2.3.2. No luck. :( Could somebody please test this with a recent 2.4-git build? Hm, it doesn't freeze here with a freshly installed 2.3.2 version. I use msvc as the compiler (which is -vc100). Please remove your installation directory/do a completely fresh install, I have a good guess that this is fixed in the patched kdelibs provided now. Closing for lack of feedback, most likely fixed, based on comment #42 aka The Answer :). Sorry, but I really have no time (and enough CPU cycles) to test source versions. I'll let you know when the next binary build will be out (I've tested nitrostemp installer but it doesn't work for me). |