Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OSRM osrm-extract Fails with tbb::captured_exception on Large OSM Files (9.9 GB, 1.1 GB) #7030

Closed
Rajakumar-Iyyemperumal opened this issue Sep 12, 2024 · 3 comments
Labels

Comments

@Rajakumar-Iyyemperumal
Copy link

Issue

I'm encountering an issue while trying to process large OSM map files using osrm-extract on a Virtual Machine running Ubuntu.
The process fails with the following error when extracting large maps like us-latest.osm.pbf (9.9 GB) and california-latest.osm.pbf (1.1 GB):

terminate called after throwing an instance of 'tbb::captured_exception'

I can able to extract and process norcal-latest.osm.pbf that is about 500 MB

Specifications

OSRM Version: 5.26.0
System: Ubuntu 20.04.6 (VM on Windows 11, allocated 6 GB RAM, 4 Processors for VM)
OSM Files: us-latest.osm.pbf (9.9 GB) and california-latest.osm.pbf (1.1 GB)
Error Message: terminate called after throwing an instance of 'tbb::captured_exception'

Questions

The process works fine for smaller map files, but fails for these larger ones. Is this a known issue with handling large maps, or are there any additional configuration settings I can try to resolve this?

Any guidance or recommendations would be greatly appreciated. Thank you!

Regards,
Rajakumar R I

@jcoupey
Copy link

jcoupey commented Sep 12, 2024

The process works fine for smaller map files, but fails for these larger ones

Hard to tell without looking at the full stack trace but you're most probably running out of RAM. 6GB is quite low to run extraction on an extract with a significant size.

@tombay
Copy link

tombay commented Sep 19, 2024

I have a ubuntu system with 16g RAM and 32g swap.
osrm-extract dach-latest.osm.pbf (5.3g) reaches a virtual peak of 49.8g.
with a RSS of 15.1g I can successfully run the extract in just over 3 hours (189 mins with usertime of 90 mins).
I imagine with only 6g it might take somewhat longer %-)

@jcoupey
Copy link

jcoupey commented Sep 20, 2024

You need to either have more RAM, or swap (could be quite slow).

@jcoupey jcoupey closed this as completed Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants