Bug 175990 - The preference dialog loads for years on MacOSX
Summary: The preference dialog loads for years on MacOSX
Status: RESOLVED DUPLICATE of bug 170195
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.0-rc
Platform: Compiled Sources macOS
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-24 15:51 UTC by Peter ZHOU
Modified: 2009-03-05 02:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter ZHOU 2008-11-24 15:51:10 UTC
Version:            (using Devel)
Compiler:          Amarok2 rc1 
OS:                OS X
Installed from:    Compiled sources

The preference dialog loads for a long time. 3-5 minutes loading time here, maybe longer.

And this is not the case for the first startup only, but everytime when I open it.
Comment 1 Mark Kretschmann 2008-11-24 20:57:27 UTC
Could you attach some debug output? Maybe it reveals interesting timing information.
Comment 2 Peter ZHOU 2008-11-25 01:20:19 UTC
Object::connect: No such signal QComboBox::textChanged(int)
Object::connect:  (sender name:   'kcfg_ExternalBrowser')
Object::connect:  (receiver name: 'settings')
amarok: BEGIN: CollectionSetup::CollectionSetup(QWidget*) 
amarok: BEGIN: QStringList MountPointManager::collectionFolders() 
amarok: END__: QStringList MountPointManager::collectionFolders() - Took 0.00023s 
amarok: END__: CollectionSetup::CollectionSetup(QWidget*) - Took 0.24s 
amarok: BEGIN: void OSDWidget::show(const QString&, QImage) 
amarok: END__: void OSDWidget::show(const QString&, QImage) - Took 0.015s 
amarok: BEGIN: virtual bool Amarok2ConfigDialog::hasChanged() 
amarok: BEGIN: virtual bool CollectionConfig::hasChanged() 
amarok: BEGIN: bool CollectionSetup::hasChanged() const 
amarok: BEGIN: QStringList MountPointManager::collectionFolders() 
amarok: END__: QStringList MountPointManager::collectionFolders() - Took 0.00019s 
amarok: END__: bool CollectionSetup::hasChanged() const - Took 0.00038s 
amarok: END__: virtual bool CollectionConfig::hasChanged() - Took 0.00049s 
amarok: BEGIN: virtual bool ServiceConfig::hasChanged() 
amarok: END__: virtual bool ServiceConfig::hasChanged() - Took 6.8e-05s 
amarok: END__: virtual bool Amarok2ConfigDialog::hasChanged() - Took 0.00088s 


nothing seems special.
Comment 3 Mark Kretschmann 2008-12-26 09:58:48 UTC
So, what's the deal with this one? Guys, it must be possible to figure out what takes so much time. 

Sprinkling the code with DEBUG_BLOCK statements is one way.


And is it still valid with SVN trunk anyway?
Comment 4 illogic-al 2009-03-05 02:21:24 UTC

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