You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# gdb /opt/osrm-backend/bin/osrm-extract
(No debugging symbols found in /opt/osrm-backend/bin/osrm-extract)
(gdb) catch throw
Catchpoint 1 (throw)
(gdb) run -p /opt/osrm-backend/share/osrm/profiles/car.lua -t 2 australia-latest.osm.pbf
Starting program: /opt/osrm-backend/bin/osrm-extract -p /opt/osrm-backend/share/osrm/profiles/car.lua -t 2 australia-latest.osm.pbf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[2025-02-07T04:12:58.518316490] [info] Parsed 0 location-dependent features with 0 GeoJSON polygons
[2025-02-07T04:12:58.518614403] [info] Using script /opt/osrm-backend/share/osrm/profiles/car.lua
[2025-02-07T04:12:58.518676689] [info] Input file: australia-latest.osm.pbf
[2025-02-07T04:12:58.518706178] [info] Profile: car.lua
[2025-02-07T04:12:58.518738012] [info] Threads: 2
[New Thread 0x7ffff65c0700 (LWP 20349)]
[New Thread 0x7ffff5dbf700 (LWP 20350)]
[2025-02-07T04:12:58.520659270] [info] Parsing in progress..
[New Thread 0x7ffff55be700 (LWP 20351)]
[New Thread 0x7ffff4dbd700 (LWP 20352)]
[Thread 0x7ffff55be700 (LWP 20351) exited]
[2025-02-07T04:12:58.524348027] [info] input file generated by pyosmium-up-to-date/3.1.3
[Thread 0x7ffff4dbd700 (LWP 20352) exited]
[2025-02-07T04:12:58.525966940] [info] timestamp: 2025-02-05T01:48:57Z
[2025-02-07T04:12:58.533083084] [info] Using profile api version 4
[2025-02-07T04:12:58.533915639] [info] Found 3 turn restriction tags:
[2025-02-07T04:12:58.533980146] [info] motor_vehicle
[2025-02-07T04:12:58.534001228] [info] motorcar
[2025-02-07T04:12:58.534020044] [info] vehicle
[2025-02-07T04:12:58.534071558] [info] Parse relations ...
[New Thread 0x7ffff4dbd700 (LWP 20353)]
[Thread 0x7ffff4dbd700 (LWP 20353) exited]
[New Thread 0x7ffff55be700 (LWP 20354)]
[New Thread 0x7fffefba2700 (LWP 20468)]
[Thread 0x7ffff55be700 (LWP 20354) exited]
[2025-02-07T04:13:09.072940225] [info] Parse ways and nodes ...
[New Thread 0x7ffff55be700 (LWP 20470)]
[New Thread 0x7ffff4dbd700 (LWP 20471)]
[Thread 0x7ffff55be700 (LWP 20470) exited]
[2025-02-07T04:13:09.088664326] [info] Using profile api version 4
[Thread 0x7ffff4dbd700 (LWP 20471) exited]
[2025-02-07T04:18:36.660313983] [info] Parsing finished after 338.14 seconds
[2025-02-07T04:18:36.660520742] [info] Raw input contains 112426581 nodes, 8827816 ways, and 11130 relations, 52773 restrictions
[2025-02-07T04:18:36.777556011] [info] Collecting way information on 52773 restrictions...ok, after 0.446604s
[2025-02-07T04:18:37.224458912] [info] Collecting way information on 40 maneuver overrides...ok, after 0.080079s
[2025-02-07T04:18:37.304726247] [info] Collecting traffic signal information on 47634 signals...[2025-02-07T04:18:38.937422733] [warn] OSM node 11961760015 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.937539898] [warn] OSM node 30880743 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.937610088] [warn] OSM node 9061042820 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.937641595] [warn] OSM node 9061042819 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.937671346] [warn] OSM node 9061042802 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.937701531] [warn] OSM node 8296618661 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.937747886] [warn] OSM node 8189842668 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.937878437] [warn] OSM node 8296618662 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.937925635] [warn] OSM node 1556534648 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.937959884] [warn] OSM node 55151225 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938056588] [warn] OSM node 4934766547 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938128735] [warn] OSM node 3344991403 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938180779] [warn] OSM node 3344991403 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938227195] [warn] OSM node 8913491581 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938279850] [warn] OSM node 7183488948 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938422937] [warn] OSM node 1867079170 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938503208] [warn] OSM node 5763133400 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938553574] [warn] OSM node 9421860855 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938666711] [warn] OSM node 8296618674 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938740041] [warn] OSM node 1843532238 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938783324] [warn] OSM node 4171855971 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938833393] [warn] OSM node 10250070099 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938881834] [warn] OSM node 1263161189 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938929082] [warn] OSM node 1867079234 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.938996121] [warn] OSM node 31319008 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939054121] [warn] OSM node 175095064 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939195966] [warn] OSM node 6505084866 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939276596] [warn] OSM node 210651224 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939370685] [warn] OSM node 1570209713 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939433675] [warn] OSM node 1140362220 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939519056] [warn] OSM node 6282174124 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939618101] [warn] OSM node 637948321 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939679812] [warn] OSM node 476970776 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939765379] [warn] OSM node 1140362305 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939807608] [warn] OSM node 1435362896 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939886283] [warn] OSM node 621549608 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939921923] [warn] OSM node 10848226035 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.939985897] [warn] OSM node 1814874999 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.940078484] [warn] OSM node 196913363 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.940211644] [warn] OSM node 8296618663 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.940424514] [warn] OSM node 572305256 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.940555717] [warn] OSM node 364000099 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.940740219] [warn] OSM node 30385497 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.940795152] [warn] OSM node 30385497 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.940845216] [warn] OSM node 35290062 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.940934264] [warn] OSM node 476970779 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.941025622] [warn] OSM node 638788644 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.941082039] [warn] OSM node 212758499 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.941130579] [warn] OSM node 9302551711 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.941217886] [warn] OSM node 11896050007 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.941293697] [warn] OSM node 261336521 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.941521395] [warn] OSM node 1277945629 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.941597221] [warn] OSM node 4365601689 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.941658961] [warn] OSM node 621549688 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.941716808] [warn] OSM node 261336520 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.941774080] [warn] OSM node 636965097 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.941862214] [warn] OSM node 363999803 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.941935262] [warn] OSM node 1834189114 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942069343] [warn] OSM node 1879154526 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942122286] [warn] OSM node 176827826 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942229274] [warn] OSM node 637948322 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942315664] [warn] OSM node 363999779 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942433869] [warn] OSM node 7604642687 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942521157] [warn] OSM node 1556534672 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942571562] [warn] OSM node 3626796061 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942621321] [warn] OSM node 1866932953 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942688618] [warn] OSM node 10107486462 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942739610] [warn] OSM node 10107486462 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942797691] [warn] OSM node 1867079231 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942848903] [warn] OSM node 1445473969 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.942965746] [warn] OSM node 4785789293 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.943071288] [warn] OSM node 1847460394 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.943117680] [warn] OSM node 202565446 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.943253268] [warn] OSM node 7171170335 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.943323710] [warn] OSM node 363999807 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.943407105] [warn] OSM node 1834189188 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.943512212] [warn] OSM node 11005426729 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.943562606] [warn] OSM node 441046724 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.943628617] [warn] OSM node 1879154424 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.943736368] [warn] OSM node 5563169787 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.943792375] [warn] OSM node 175096898 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.943839324] [warn] OSM node 30101185 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.943905772] [warn] OSM node 5822538011 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.944056763] [warn] OSM node 6471368662 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.944116043] [warn] OSM node 8450752786 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.944159331] [warn] OSM node 6292541241 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.944198333] [warn] OSM node 11733702661 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.944305155] [warn] OSM node 1881357117 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.944444784] [warn] OSM node 8263105328 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.944492910] [warn] OSM node 8263105328 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.944539476] [warn] OSM node 248746964 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.944619741] [warn] OSM node 32999019 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.944674006] [warn] OSM node 2313669791 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.944779852] [warn] OSM node 3914060652 has a unidirectional traffic signal ambiguously applied to multiple ways
[2025-02-07T04:18:38.944831212] [warn] OSM node 60303501 has a unidirectional traffic signal ambiguously applied to multiple ways
ok, after 1.64014s
[2025-02-07T04:18:38.948007506] [info] Sorting used nodes ... ok, after 1.125s
[2025-02-07T04:18:40.073168258] [info] Erasing duplicate nodes ... ok, after 0.064654s
[2025-02-07T04:18:40.137953081] [info] Sorting all nodes ... ok, after 0.14335s
[2025-02-07T04:18:40.281503318] [info] Building node id map ... ok, after 0.42848s
[2025-02-07T04:18:40.710183278] [info] Confirming/Writing used nodes ... ok, after 0.961711s
[2025-02-07T04:18:41.672069058] [info] Writing barrier nodes ... ok, after 0s
[2025-02-07T04:18:41.682253412] [info] Processed 15409755 nodes
[2025-02-07T04:18:41.682372010] [info] Sorting edges by start ... ok, after 1.78434s
[2025-02-07T04:18:43.466893577] [info] Setting start coords ... ok, after 2.03814s
[2025-02-07T04:18:45.505208581] [info] Sorting edges by target ... ok, after 1.77479s
[2025-02-07T04:18:47.280186035] [info] Computing edge weights ... ok, after 5.01016s
[2025-02-07T04:18:52.290553907] [info] Sorting edges by renumbered start ... ok, after 1.93065s
[2025-02-07T04:18:54.822836540] [info] Writing used edges ... ok, after 0.626304s -- Processed 16114217 edges
[2025-02-07T04:18:55.449406462] [info] Preparing traffic light signals for 6701 bidirectional, 39937 unidirectional nodes ...ok, after 0.108722s
[2025-02-07T04:18:55.558327395] [info] Collecting node information on 40 maneuver overrides...ok, after 0.00019s
[2025-02-07T04:18:55.558795779] [info] Collecting node information on 52773 restrictions...ok, after 0.199694s
[2025-02-07T04:18:55.758656784] [info] writing street name index ... ok, after 0.026765s
[2025-02-07T04:18:55.822896996] [info] extraction finished after 357.304s
[Thread 0x7ffff5dbf700 (LWP 20350) exited]
[Thread 0x7ffff65c0700 (LWP 20349) exited]
[2025-02-07T04:18:56.903581724] [info] Generating edge-expanded graph representation
[2025-02-07T04:19:04.898407816] [info] . 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100%
[2025-02-07T04:19:52.998843028] [info] Node compression ratio: 0.159027
[2025-02-07T04:19:52.999164888] [info] Edge compression ratio: 0.194365
[2025-02-07T04:20:16.658698235] [info] graph compression removed 1544155 annotations of 1826168 in 7.5388 seconds
[2025-02-07T04:20:16.751705799] [info] Find segregated edges in node-based graph ...
[2025-02-07T04:20:32.025771395] [info] ok, after 15.2727s
[2025-02-07T04:20:32.025898199] [info] Segregated edges count = 117643
[2025-02-07T04:20:32.025931690] [info] Writing nodes for nodes-based and edges-based graphs ...
[2025-02-07T04:20:33.666055896] [info] Geometry successfully removed:
compressed edges: 6253000
compressed geometries: 32230132
longest chain length: 4191
cmpr ratio: 0.194011
avg chain length: 5.15435
[2025-02-07T04:20:33.666235982] [info] Removing invalid turn restrictions...removed 7 invalid turn restrictions, after 0.032232s
[2025-02-07T04:20:33.699950265] [info] Removing invalid maneuver overrides...removed 0 invalid maneuver overrides, after 2.7e-05s
[2025-02-07T04:20:33.701557594] [info] Constructing restriction graph on 51400 restrictions...ok, after 0.055516s
[2025-02-07T04:20:35.337604424] [info] Generating edge expanded nodes ...
[2025-02-07T04:20:35.338692933] [info] . 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100%
[2025-02-07T04:20:41.279006140] [info] Expanding via-way turn restrictions ...
[2025-02-07T04:20:41.279054447] [info] . 10% . 20% . 30% . 40% . 50% . 60% . 70% . 80% . 90% . 100%
[2025-02-07T04:20:41.302185568] [info] Generated 5592749 nodes (11670 of which are duplicates) and 16098796 segments in edge-expanded graph
[2025-02-07T04:20:41.472756808] [info] Generating edge-expanded edges
Thread 1 "osrm-extract" received signal SIGSEGV, Segmentation fault.
0x00000000006ade3a in osrm::extractor::UnresolvedManeuverOverride::Turns() const ()
Missing separate debuginfos, use: debuginfo-install libgcc-4.8.5-44.el7.x86_64 libstdc++-4.8.5-44.el7.x86_64
(gdb) bt
#0 0x00000000006ade3a in osrm::extractor::UnresolvedManeuverOverride::Turns() const ()
#1 0x00000000006a50ac in osrm::extractor::EdgeBasedGraphFactory::GenerateEdgeExpandedEdges(osrm::extractor::ScriptingEnvironment&, std::string const&, std::string const&, std::string const&, std::string const&, std::string const&, osrm::extractor::NodeRestrictionMap<osrm::extractor::UnconditionalOnly> const&, osrm::extractor::NodeRestrictionMap<osrm::extractor::ConditionalOnly> const&, osrm::extractor::WayRestrictionMap const&, std::vector<osrm::extractor::UnresolvedManeuverOverride, std::allocator<osrm::extractor::UnresolvedManeuverOverride> > const&) ()
#2 0x00000000006a8488 in osrm::extractor::EdgeBasedGraphFactory::Run(osrm::extractor::ScriptingEnvironment&, std::string const&, std::string const&, std::string const&, std::string const&, std::string const&, std::string const&, osrm::extractor::NodeRestrictionMap<osrm::extractor::UnconditionalOnly> const&, osrm::extractor::NodeRestrictionMap<osrm::extractor::ConditionalOnly> const&, osrm::extractor::WayRestrictionMap const&, std::vector<osrm::extractor::UnresolvedManeuverOverride, std::allocator<osrm::extractor::UnresolvedManeuverOverride> > const&) ()
#3 0x000000000054f11e in osrm::extractor::Extractor::BuildEdgeExpandedGraph(osrm::util::DynamicGraph<osrm::util::NodeBasedEdgeData> const&, std::vector<osrm::util::Coordinate, std::allocator<osrm::util::Coordinate> > const&, osrm::extractor::CompressedEdgeContainer const&, std::unordered_set<unsigned int, std::hash<unsigned int>, std::equal_to<unsigned int>, std::allocator<unsigned int> > const&, osrm::extractor::TrafficSignals const&, osrm::extractor::RestrictionGraph const&, std::unordered_set<unsigned int, std::hash<unsigned int>, std::equal_to<unsigned int>, std::allocator<unsigned int> > const&, osrm::extractor::detail::NameTableImpl<(osrm::storage::Ownership)0> const&, std::vector<osrm::extractor::UnresolvedManeuverOverride, std::allocator<osrm::extractor::UnresolvedManeuverOverride> > const&, osrm::util::ConcurrentIDMap<std::vector<unsigned short, std::allocator<unsigned short> >, unsigned short, osrm::extractor::TurnLaneDescription_hash> const&, osrm::extractor::ScriptingEnvironment&, osrm::extractor::detail::EdgeBasedNodeDataContainerImpl<(osrm::storage::Ownership)0>&, std::vector<osrm::extractor::EdgeBasedNodeSegment, std::allocator<osrm::extractor::EdgeBasedNodeSegment> >&, std::vector<int, std::allocator<int> >&, std::vector<int, std::allocator<int> >&, std::vector<float, std::allocator<float> >&, osrm::util::DeallocatingVector<osrm::extractor::EdgeBasedEdge>&, unsigned int&) ()
#4 0x0000000000557195 in osrm::extractor::Extractor::run(osrm::extractor::ScriptingEnvironment&) ()
#5 0x0000000000548921 in osrm::extract(osrm::extractor::ExtractorConfig const&) ()
`#6` 0x00000000005386cd in main ()
We had no problems extracting this dataset until now, the last successful extract was on 2024-12-31 and we noticed the problem starting with 2025-02-01
We've tested on the separate OSM data from AU states: https://download.openstreetmap.fr/extracts/oceania/australia/
new_south_wales-latest.osm.pbf
northern_territory-latest.osm.pbf
queensland-latest.osm.pbf
south_australia-latest.osm.pbf
tasmania-latest.osm.pbf
victoria-latest.osm.pbf
western_australia-latest.osm.pbf
and these are extracted correctly individually, but if merged together the problem appears:
$ osmium merge *.pbf -o australia-latest.pbf
started excluding state by state, and the problematic one seems to be: new_south_wales-latest.osm.pbf
With that left out the problem disappears.
Maybe some relation to: 6625
Does anyone have an idea on how we could work around this problem?
Thanks!
The text was updated successfully, but these errors were encountered:
Hello,
Recent data from http://download.geofabrik.de/australia-oceania/australia.html (australia-latest.osm.pbf) triggers segfault on osrm-extract with car.lua
OSRM build: 5.27.1
OS: CentOS 7 + devtoolset-9
Backtrace:
We had no problems extracting this dataset until now, the last successful extract was on 2024-12-31 and we noticed the problem starting with 2025-02-01
We've tested on the separate OSM data from AU states:
https://download.openstreetmap.fr/extracts/oceania/australia/
new_south_wales-latest.osm.pbf
northern_territory-latest.osm.pbf
queensland-latest.osm.pbf
south_australia-latest.osm.pbf
tasmania-latest.osm.pbf
victoria-latest.osm.pbf
western_australia-latest.osm.pbf
and these are extracted correctly individually, but if merged together the problem appears:
$ osmium merge *.pbf -o australia-latest.pbf
started excluding state by state, and the problematic one seems to be: new_south_wales-latest.osm.pbf
With that left out the problem disappears.
Maybe some relation to: 6625
Does anyone have an idea on how we could work around this problem?
Thanks!
The text was updated successfully, but these errors were encountered: