[mkgmap-dev] Memory Full - with newest mkgmap versions appearing again
From Felix Hartmann extremecarver at gmail.com on Fri May 29 17:55:48 BST 2015
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 at 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 at 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20150529/c7e81102/attachment.html>
- Previous message: [mkgmap-dev] Memory Full - with newest mkgmap versions appearing again
- Next message: [mkgmap-dev] Splitter problem: losing a track segment
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list