Custom Query (1067 matches)


Show under each result:

Results (106 - 108 of 1067)

Ticket Resolution Summary Owner Reporter
#1155 fixed Maptool memory usage optimization tryagain tryagain
Description It looks like we have hit our hardware limits with maptool. It has now peak memory consumption above 10G, but server cant give it so much.

That might be related to osm growth, our recent code changes.

I'm aware of memory leaks in the relation processing code, and will attempt to address them when i get to my dev environment next week.

For now, i see two possible solutions, one is to split maptool run into two parts with -s and -e options to drop any leaks between runs. If that won't help, i will try to reduce -S value (slice size), which though might increase processing time.

I do not think that increasing swap size is a way to go, but depending on how efficiently we'll be able to address memory apettites of maptool, server might require a memory upgrade.

#1154 fixed Fix all compiler warnings KaZeR sleske
Description The Navit build activates compiler warnings (flag -Wall). This is good :-).

However, what's not so good is that apparently no one reads and fixes them, which makes them rather pointless. For example, the current nightly build on Ubuntu produces about 180 (!) warnings.

This should be fixed, so if code changes cause a warning, it will stand out and get attention.
#1153 fixed bug on version 0.0.4 resolved KaZeR jcaaa0228
Note: See TracQuery for help on using queries.