| Summary: | The preference dialog loads for years on MacOSX | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Peter ZHOU <peterzhoulei> |
| Component: | general | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | illogical1, lfranchi |
| Priority: | NOR | ||
| Version First Reported In: | 2.0-rc | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Peter ZHOU
2008-11-24 15:51:10 UTC
Could you attach some debug output? Maybe it reveals interesting timing information. 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. 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? *** This bug has been marked as a duplicate of bug 170195 *** |