-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Description
Hi,
when working on post-processing positioning (function postpos in postpos.c) there is the possibility to end up with memory leak. In particular, in function execses (in postpos.c) there is a call to function readobsnav(): inside this function the library tries to read both observation and navigation files. If the reading fails the function returns immediately 0 and does not call function freeobsnav() to delete obss and navs.
Case: I upload an observation file and no navigation file. The library load all obs, but fails when trying to read the nav data. Thus, the memory has been allocated for all the obs but it is not freed after failure.
Since I'm running several post-processing every time readobsnav() fails memory increases. In the following three memory snapshots after three failures



