Memory Full - with newest mkgmap versions appearing again
I've got now 3 reports in - that with my maps the memory full bug is back again (remember around 3 years ago - when the more mkgmap maps (or non NT garmin City Navigator) with index you sent to your device - the more often/likely it would appear. Well - it seems some mkgmap change is causing it again. So far I got reports from Montana 600 and Oregon 300 users - all on newest firmware. Anyone else having probs - getting feedback? Any idea what change in mkgmap caused it? (seems garmin did not really fix it correctly but just worked around it with their firmwares). Felix -- Felix Hartman - Openmtbmap.org & VeloMap.org Floragasse 9/11 1040 Wien Austria - Österreich
Hi Felix isn't it device problem? It happens to me form time to time, I have always assumed, that device remembers all map-id (tile id) ever used and sometimes gets no memory for a new one. Device reset cures this problem. Maybe you have changed range of map id for some maps and this caused more problems for users who loads updates? -- Best regards, Andrzej
Nope - I did not change anything major last 10 months besides mkgmap versions - hence that's why I believe there is a new problematic thing... On 29 May 2015 at 13:04, Andrzej Popowski <popej@poczta.onet.pl> wrote:
Hi Felix
isn't it device problem? It happens to me form time to time, I have always assumed, that device remembers all map-id (tile id) ever used and sometimes gets no memory for a new one. Device reset cures this problem.
Maybe you have changed range of map id for some maps and this caused more problems for users who loads updates?
-- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Openmtbmap.org & VeloMap.org Floragasse 9/11 1040 Wien Austria - Österreich
participants (2)
-
Andrzej Popowski -
Felix Hartmann