I observed this really strange error when running

./pants export

with

--no-pantsd

. Is this expected?

[BOOTSTRAP] [INFO] Sending command: /home/jtilahun/devel/monorepo/pants --print-stacktrace --no-export-symlink-python-virtualenv --no-pantsd export --resolve=python-default
[BOOTSTRAP] [WARNING] Received non-zero return code (-6) from /home/jtilahun/devel/monorepo/pants --print-stacktrace --no-export-symlink-python-virtualenv --no-pantsd export --resolve=python-default
[BOOTSTRAP] [WARNING] STDOUT: 
[BOOTSTRAP] [WARNING] STDERR: /github/home/.cargo/git/checkouts/lmdb-rs-369bfd26153a2575/6ae7a55/lmdb-sys/lmdb/libraries/liblmdb/m:2126: Assertion 'rc == 0' failed in mdb_page_dirty()

No, that is definitely not expected

For context, I've been encountering

native_engine.PantsdClientException: The pantsd process was killed during the run.

If this was not intentionally done by you, Pants may have been killed by the operating system due to memory overconsumption (i.e. OOM-killed). If you keep seeing this error message, try the troubleshooting steps below. If none of those help, please consider filing a GitHub issue or reaching out on Slack so that we can investigate the possible memory overconsumption (<https://www.pantsbuild.org/docs/getting-help>).
 - Exit other applications, including applications running in the background.
 - Set the global option `--pantsd-max-memory-usage` to reduce Pantsd's memory consumption by retaining less in its in-memory cache (run `./pants help-advanced global`).
 - Disable pantsd with the global option `--no-pantsd` to avoid persisting memory across Pants runs, although you will miss out on additional caching.

all the time recently. I tried the first two bullet points to no avail, which is why I tried

--no-pantsd

. Adding

--no-pantsd

led to the strange error

How much RAM does your system have? Is this running in a docker container, for example?

My system has 16 GB of RAM. This is running directly, not in a container

And - not trying to be funny here - does this persist if you reboot?

This persists when I reboot. Even after a reboot, I get the OOM-killed error without

--no-pantsd

and then I get the strange error adding

--no-pantsd

Looks like you'll have to investigate why your system is killing pantsd (OOM or other reason), because you really need pantsd on for performance. But separately, sounds like Pants (without pantsd) is hitting an lmdb bug, which I see mentioned in other contexts, e.g., https://github.com/bmatsuo/lmdb-go/issues/131

I filed this GitHub issue: https://github.com/pantsbuild/pants/issues/18726. I honestly don't know what's happening on my computer. I wouldn't be surprised if this is just a me-problem. But the error message is so cryptic and I've tried this many, many times to no avail

Very very weird