Closed chatelao closed 1 year ago
The problem is that I can't predict the necessary amount of memory up front, it depends on too many different factors.
There even seem to be some cases where small render areas lead to this for certain polygon fill styles, although I was not able to fully track this down yet.
What I can probably do is to catch the "out of memory" exception and replace the standard exception output with a more user friendly error message describing the problem ...
The MapOSMatic web frontend now has a more clear error message:
For command line users the backtrace output should be clear enough.
For the out-of-memory errors on rather small map areas see #66 now
https://maposmatic.osm-baustelle.de/results//2022/03/16/210149_2022-03-16_12-06_ukraine-errors.txt