-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Cannot process planet-latest.osm.pbf #1820
Comments
Which version are you using? Latest |
then latest, commit c381834 osrm-extract -v gives v4.8.1 |
For the record: source location at that commit. This is a good start to gather more information:
|
I had updated to commit 9a332d2 before running. In this commit osrm-extract finished successfully, with the following AddressSanitizer info: ==22735==ERROR: LeakSanitizer: detected memory leaks Direct leak of 6168 byte(s) in 3 object(s) allocated from: Direct leak of 162 byte(s) in 9 object(s) allocated from: SUMMARY: AddressSanitizer: 6330 byte(s) leaked in 12 allocation(s). |
@krk does this work now for you? |
It was working until I had to restart the server. Now executing osrm-routed gives the following warning. [warn] Shared memory settings conflict with path settings. |
@krk how do you start the server? |
without any parameters, while in the folder that contains processed files. |
From the error message I see that you are specifying both 1/ the base path to an osrm-backend/include/util/routed_options.hpp Lines 253 to 256 in f682476
Maybe you have a ini configuration file where these parameters are coming from. Please try without the shared memory option. |
@krk any news on this? If your problem is fixed, feel free to close here. |
There was no ini file, I wasn't supplying any shared memory options, problem was not fixed. Closing this issue, will open a new one when I try a later version or a stable version. Thanks for your quick responses. |
Planet cannot be processed with the error message after 30 hours: "free(): invalid size". This is the third try.
What would you suggest to be able to successfully process the planet file?
Configuration: 224 GB RAM 16 cores and 600 GB free disk space.
The text was updated successfully, but these errors were encountered: