Closed cdrum closed 7 years ago
OK, Chris, thanks for the report. I’ll file a bug on this. One of our developers has been digging into the dump1090 javascript files looking for a memory leak, so she’ll probably be able to gain some insight on this pretty quickly.
-karl
On Nov 14, 2014, at 4:01 PM, Chris Drumgoole notifications@github.com<mailto:notifications@github.com> wrote:
Not sure if you know this, and it's probably a minor thing, but when looking at the local map (:8080) on my laptop, letting it pick up a bunch of planes, then I shut my laptop for a while, later when I open it again, the map doesn't seem to remove the old planes.
— Reply to this email directly or view it on GitHubhttps://github.com/flightaware/piaware/issues/5.
This is basically because the client-side javascript relies on the dump1090-provided "seen" counters to decide when to hide/expire aircraft.
If the client is suspended for long enough, then the aircraft record will expire on the dump1090 side without the client ever seeing an update that has a large-enough seen value for it to be expired on the client.
This was fixed in dump1090-mutability a long time ago, and now that dump1090-fa is based on that, we have the bugfix in the standard piaware images too.
Not sure if you know this, and it's probably a minor thing, but when looking at the local map (:8080) on my laptop, letting it pick up a bunch of planes, then I shut my laptop for a while, later when I open it again, the map doesn't seem to remove the old planes.