Bug 324936 - Marble needs 100% CPU after close Marble
Summary: Marble needs 100% CPU after close Marble
Status: RESOLVED WORKSFORME
Alias: None
Product: marble
Classification: Applications
Component: general (show other bugs)
Version: 1.5 (KDE 4.10)
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-15 17:52 UTC by Carioca
Modified: 2014-12-13 19:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Carioca 2013-09-15 17:52:19 UTC 
Marble does not close, it stays in background and after some time start taking 100% CPU load. Does not happen when I did not search a route.

Reproducible: Always

Steps to Reproduce:
1. search a route in Marble
2. close Marble
3. check CPU load of tasks
Actual Results:  
Marble needs 100% CPU load in background

Expected Results:  
exit Marble
Comment 1 Illya Kovalevskyy 2014-12-13 19:33:00 UTC 
I am doing bug triaging as Google Code-In 2014 student.

Can't reproduce this on latest marble master, it finishes as expected.
Comment 2 Myriam Schweingruber 2014-12-13 19:47:04 UTC 
By comment #1 this is not reproducible. Please feel free to reopen if it should happen again, ideally with a valgrind trace if it is reproducible with current git master or the upcoming release.