Works at my side. Please check if some other process is killing it.

If no process interfering OneDev, please let me know detail steps to reproduce the issue.

Solved. OneDev was stopped by the Linux OOM killer.

So the issue was not the export but rather the spike of the memory usage right after startup, due to having a lot of cross-issue links.

Bumping the RAM in the VM dedicated to OneDev to 16GB made it start normally.

I guess this is worth mentioning in the documentation somewhere, but at least it's now Googleable.

16G mem seems quite a lot for OneaDev. Curious how many issues you have in OneDev.

Well I was using my personal instance as an impromptu database so I generated "eternal" issues for items like countries, cities and eg my subscription payments, and that bumps the total count to somewhere around 1500 (plus about 4000 extra created due to script bugs and then removed).

The OOM happened with 8G of RAM and I just doubled it to be sure.

It is odd that this number of issues can lead to OOM in OneDev. I tested with 100k issues with default memory setting (use less than 1G mem). It will help a lot if you can create an example database demonstrating the issue.

Closing this for now, feel free to reopen if there is more info.