| Summary: | Amarok crashes when re-opening the Manage Scripts window [@ QScriptEngine::isEvaluating] | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Hagai Kariti <hkariti> |
| Component: | Tools/Script Manager | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | dedeibel.forum, kfunk, rkeevil+kde, rnet723, thomas |
| Priority: | NOR | ||
| Version: | 2.4.1 | ||
| Target Milestone: | 2.4.2 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.4.2 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Hagai Kariti
2011-03-19 22:14:59 UTC
*** Bug 272477 has been marked as a duplicate of this bug. *** Created attachment 60082 [details]
New crash information added by DrKonqi
amarok (2.4.1) on KDE Platform 4.6.3 (4.6.3) "release 4" using Qt 4.7.3
- What I was doing when the application crashed:
I've installed some scripts using "Managed Scripts", and Amarok crashed when I pressed ctrl+q to quit amarok.
-- Backtrace (Reduced):
#6 d_func (this=0x0) at api/qscriptengine.h:280
#7 QScriptEngine::isEvaluating (this=0x0) at api/qscriptengine.cpp:4105
#8 0x00007f8c0b2ac62b in ScriptManager::slotStopScript (this=0x18d1850, name=...) at /usr/src/debug/amarok-2.4.1/src/ScriptManager.cpp:292
#9 0x00007f8c0b2ae665 in ScriptManager::stopScript (this=0x18d1850, name=...) at /usr/src/debug/amarok-2.4.1/src/ScriptManager.cpp:116
#10 0x00007f8c0accc5d6 in ScriptsConfig::slotManageScripts (this=0x325deb0) at /usr/src/debug/amarok-2.4.1/src/configdialog/dialogs/ScriptsConfig.cpp:73
Confirmed by comment #2 Created attachment 60589 [details]
New crash information added by DrKonqi
amarok (2.4.1) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.3
- What I was doing when the application crashed:
Crashed after clicking on Manage Scripts, after looking at the information page of an already installed script.
-- Backtrace (Reduced):
#6 data (this=0x0) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
[...]
#8 d_func (this=0x0) at api/qscriptengine.h:280
#9 QScriptEngine::isEvaluating (this=0x0) at api/qscriptengine.cpp:4105
#10 0x00007f1e8183ec30 in ScriptManager::slotStopScript (this=0x4063200, name=...) at ../../src/ScriptManager.cpp:292
#11 0x00007f1e81840c95 in ScriptManager::stopScript (this=0x4063200, name=...) at ../../src/ScriptManager.cpp:116
Git commit fcc420cf453d0c2b0d56f35584651f3b956f62dd by Kevin Funk. Committed on 03/06/2011 at 23:43. Pushed by kfunk into branch 'master'. Fix crash by invalid scripts during stop phase Example scenario: Script activated -> Syntax Error -> Manager tries to stop the script -> Crash due to missing script engine FIXED-IN: 2.4.2 BUG: 268917 M +2 -0 ChangeLog M +7 -1 src/ScriptManager.cpp http://commits.kde.org/amarok/fcc420cf453d0c2b0d56f35584651f3b956f62dd Created attachment 61605 [details]
New crash information added by DrKonqi
amarok (2.4.1) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.3
- What I was doing when the application crashed:
- Open the Manage Window
- Close it
- Open it
- While it was opening (not yet showing) I clicked the button again. But I guess it was already failing then.
I guess in my version it wasn't fixed yet but looking forward to updating. Thanks :D
-- Backtrace (Reduced):
#6 data (this=0x0) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
[...]
#8 d_func (this=0x0) at api/qscriptengine.h:280
#9 QScriptEngine::isEvaluating (this=0x0) at api/qscriptengine.cpp:4105
#10 0x00007f4558206c30 in ScriptManager::slotStopScript (this=0x20c4110, name=...) at ../../src/ScriptManager.cpp:292
#11 0x00007f4558208c95 in ScriptManager::stopScript (this=0x20c4110, name=...) at ../../src/ScriptManager.cpp:116
@Benjamin: Please test with the upcoming 2.4.2 rc. Should be fixed. |