ZeroG wrote:
> Same stacktrace experienced 7 times since rev 125 (30/01)
> 4 times by Stan
> 1 by Chris
> 1 by another user (on Android 2.0.1)
>
> Revs 125, 133, 139
>
> There is some kind of memory leak in the GPS trace code.
Is this something we can track back to code in release 125? Will it be difficult to diagnose? Would anyone like to lead on this?
ZeroG wrote:
> Same stacktrace experienced 7 times since rev 125 (30/01)
> 4 times by Stan
> 1 by Chris
> 1 by another user (on Android 2.0.1)
>
> Revs 125, 133, 139
>
> There is some kind of memory leak in the GPS trace code.
Is this something we can track back to code in release 125? Will it be difficult to diagnose? Would anyone like to lead on this?
Chris.