Andrew Ashikhmin

@chfast It looks to me like https://github.com/vorot93/evmodin/pull/2 is relevant here. @vorot93 what was the reason behind this change? Was `async` too slow?

@AlexeyAkhunov @tjayrush Is it still an issue or can we close it?

I remember we had to bump machine class in our gcc CI builds; that was also probably related to memory. So I'd say it's a valid issue, we should probably...

Implemented in PRs #4671, #5479, #5487, #5488, #5600, #5617, #5645, #5685, #5700, #5717, #5737, #5783, #5798, #5820, #5873, #5929, #5989, and #5997.

There's also `SILKWORM_ASSERT`, which is checked even if `NDEBUG` is defined.

We've added support of execution with Silkworm in https://github.com/ledgerwatch/erigon/pull/8353. Check it out using flags `--silkworm.path` and `--silkworm.exec`, but please bear in mind that it's very experimental and we're actively working...

Please re-open if the issue still happens with [v2.59.2](https://github.com/ledgerwatch/erigon/releases/tag/v2.59.2) or later.

Please re-open if it's still the case with [v2.59.0](https://github.com/ledgerwatch/erigon/releases/tag/v2.59.0)

And another crash: 

In my app the invocation of "self.topLayoutGuide.length" itself in maximumAvailableHeightWithSize causes UIViewAlertForUnsatisfiableConstraints, while "self.view.safeAreaInsets.top" works fine. I'm running under Xcode 10 beta 4 though, haven't tried under Xcode 9. I'll...