It is not clear this is a necessary or sufficient fix without a valid specific trigger.

I’ve updated the test that should also make the need for the view->buf NULL check clearer.

The issue is moot since this has been closed, but I'm afraid this still wouldn't have been useful. Your fix is unrelated to the test; it passes with or without it. It is good practice to always run your test scripts against affected versions, to confirm it reproduces the bug. Without that you don't know the testworks.

Also note the bug in the OP is aSIGBUS, a fatal signal. It is completely expected that invalid operations like this raise exceptions, but it shouldn't be possible to trigger a fatal signal via the public API^{-ish. Terms and conditions apply. Offer void whenctypes ormmap orgc or various other low-level power tools.}