Could you add a bug-report for this? In my pov, this is a critical bug and should be addressed by 4.6.2. It might even be considered severe enough for a recall of 4.6.1. A lot of companies use our plugin structure and if this is an issue, that is a dealbreaker for a lot of them
It's definitely not good, although that fix was needed to solve a crasher that was introduced in the 4.6.0 dev cycle. While the proper thing to do was likely to revert the offending commit instead of backporting the fix, at this point I am unsure about the best way to fix it. If there has been more than one 4.6.x release before the incompatibly it would be somewhat different, but now either way there will be exactly one 4.6 release not compatible with the others.
John