Thanks for the explanation and the fix Gerd!



Hi Minko,

well, yes, the problem is caused by an extreme density of (Garmin) route restrictions. Those are created for OSM turn restrictions and also for barriers when --link-pois-to-ways is used. Maybe this area contains many type=restriction relations with via ways, those require more bytes compared to simple turn restrictions with one via node.
I think the fix in r4805 is the better alternative compared to using --ignore-turn-restrictions.

Gerd