GSoC/GCI Archive
Google Code-in 2014 KDE

Marble: Check Marble for memory leaks and fix a leak

completed by: Ilya Kowalewski

mentors: Dennis Nienhüser, shentey, Sanjiban Bairagya, Torsten Rahn

Please use valgrind (and possibly kcachegrind) with Marble:

Check for memory leaks. First try finding a possible leak during regular Marble startup.

Fix one leak if there is one. If there is none during startup, then try to find one during regular use of Marble and create a fix.

Attach the valgrind output with all leaks found to this task.