Forums
(@seblito)
3 years ago
Version 4.0.5 resolved this issue.
Update
I rolled back to version 4.0.3 today and the fatal error disappeared, so yes I would say this is an actual bug.