This might be related to the upstream bug on sf.net https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1670475&group_id=93438 as OSM data suffers from occasional bad UTF-8 characters. When Inkscape encounters those it will allocate all available RAM in order to process it, and because that fails, crash.
This might be related to the upstream bug on sf.net /sourceforge. net/tracker/ ?func=detail& atid=604306& aid=1670475& group_id= 93438
https:/
as OSM data suffers from occasional bad UTF-8 characters.
When Inkscape encounters those it will allocate all available RAM in order to process it, and because that fails, crash.