Kamil Ignacak
2017-07-23 20:28:04 UTC
Hi!
I think that I've found two minor memory leaks in recent viking code.
Can you please take a look?
1.
The leak happens when a_get_viking_data_home() function is called in
modules.c: value returned by this function is not deallocated.
2.
The leak happens in waypoint code: destructor function
vik_waypoint_free() doesn't deallocate "name" field, even though the
field is set using g_strdup() function.
Best regards,
Kamil
I think that I've found two minor memory leaks in recent viking code.
Can you please take a look?
1.
The leak happens when a_get_viking_data_home() function is called in
modules.c: value returned by this function is not deallocated.
2.
The leak happens in waypoint code: destructor function
vik_waypoint_free() doesn't deallocate "name" field, even though the
field is set using g_strdup() function.
Best regards,
Kamil