The .osm file successfully opens if i use Files->Open menu option but crashes when i use the open options from Edit Maps panel. Reproducible: Always Steps to Reproduce: 1.Create a .osm file by editing the file from the Edit Maps Panel 2.Try to open the same file use open option in the panel 3.Marble Crashes
Created attachment 96299 [details] the .osm file that causes the crash
Seems to be some kind of race condition. Commenting m_parsingTasks[i]->deleteLater(); in ParsingRunnerManager::Private::cleanupParsingTask works around it.
Git commit 31f7b982736eaece5a8d9958f1aca06dedc630be by Dennis Nienhüser. Committed on 16/01/2016 at 15:57. Pushed by nienhueser into branch 'master'. Fix a crash when using the blocking API of ParsingRunnerManager Both QThreadPool and ParsingRunnerManager were trying to delete the same class instance. Now ParsingRunnerManager only keeps track of the number of active parsers, but does not attempt to delete them once they finish. A simpler fix would have been to call setAutoDelete(false) in the ParsingTask ctor, but this approach seems cleaner. M +15 -19 src/lib/marble/ParsingRunnerManager.cpp M +1 -2 src/lib/marble/ParsingRunnerManager.h M +1 -1 src/lib/marble/RunnerTask.cpp M +1 -1 src/lib/marble/RunnerTask.h http://commits.kde.org/marble/31f7b982736eaece5a8d9958f1aca06dedc630be
Thank you for the report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!