We have fixed this one; will be ready in the next update.
Although even we have tested large codebases by ourselves, it is possible there will occur a similar problem somewhere else - in such a case - we'll be glad for the stack traces again.
Thank you!