Peter Johnson

Could you please add some instrumentation to capture the query causing the segfault if possible? From what I'm seeing here it's difficult to resolve this issue without knowing which version(s)...

After some trial and error I was able to get `846cd5bdb6db` to segfault by increasing the input query length, this is the query which finally caused it to fail on...

What I'll do is to revert to the last known stable version and write up an issue on the libpostal repo to make them aware, it seems to be affecting...

Okay, bad news, I rebuilt this image pinned to an older version of our libpostal baseimage and I was still able to trigger the segfault by sending 5 to 10...

It's not clear *when exactly* the regression was introduced but I checked out an old version from `2021-11-03` and it isn't affected, so that can provide a bookend for the...

In fact there have been fairly few releases since 2021 due to not much activity on the upstream repos:

Hi @michaelkirk, yeah I think we'll definitely like to keep up with major releases at some point so thanks for all your work 🙇 Honestly I'm still feeling the pain...

> The work I've done is still compatible with elastic7. Does that change the equation for you? That's great, I am 👍 for dropping support for 6 so we can...

Thanks for the continued reports, they are helpful to discover which versions are affected. These memory issues are being discussed over on the main libpostal issue tracker and we hope...

@mreid-exiger are you sure that https://hub.docker.com/layers/pelias/libpostal-service/master-2021-11-03-aaf0586c78acd54e4586d84e6257c56b9db99f3e/images/sha256-ca4ffcc5e2f8d415b6d72cce6c32ebfcf7142648b337e8c68a13f2827708e62a?context=repo is crashing?