When using libosrm, the profile values for vehicles have to match the dataset names used when loading data using osrm-datastore. When a wrong profile value is used in input, we catch the OSRM error and pass it on to generate a custom error that looks like:

{"code":3,"error":"Invalid shared memory region: foo"}

This unnecessarily exposes the OSRM internals and is especially not very helpful for end users. The right feedback should be:

{"code":3,"error":"Invalid profile: foo"}

which is also what we return when using osrm-routed.