This might be something that was fixed by 39b89a18a8c357151a173ab02dc95dff1f02715d -- the trace looks a bit similar to the other reports. If you have a chance to try it, a report of result would be appreciated. Iirc, patch not ported to branch 5.0 yet, but should be done when releasing the last version in 5.0.x series, and that should be in the near future.