@Mentalist Traceur: I implemented the workaround mentioned above (using a rectangular bbox instead of the large polygons), it will be available in RC 2. Please report if the behavior gets better. Independent of that, can you please check the memory consumption of Marble? Use e.g. htop. Best measure it first on startup and then when the routing config dialog is opened (which will trigger the loading of monav maps). The memory usage here should decrease significantly with RC 2, so it'd be good to have some numbers before installing that. I can't test it myself currently, had to send in my N900 for repair today (USB port is broken).

@Estel: We don't do any unusual/low level memory management. I think an out-of-memory situation will occur earlier than occupying all physically installed memory - the memory is shared with other application and the operating system.

@gazza_d: Can you send me a link to the problematic roundabout (preferably using openstreetmap.org). I'll look into the data to see what's going wrong there.

@Fellfrosch: We've got one German contribution so far, but the more, the better!
There's no manual routing implemented and kml editing is on the todo list, but so far nobody worked on it.

@vi_: As discussed on IRC the .dgml file syntax needs to be correct xml. I just fixed the crash in Marble though, so loading a syntactically incorrect .dgml file will now (RC 2) not result in a crash. The map will be ignored instead. Starting "/opt/marble/bin/marble.sh --debug-info" will give you a warning in the shell in that situation.