This seems to be a scope problem. Are you sure that you use the latest snapshot of core-js?
It would really help if you could reduce the problem (testing with web.de currently means 151.68 KB!). If you want to start looking at it with a debugger, a first step would be to verify the scopes of the Function objects involved when the exception arise. Additionally you can use the FalsifyingWebConnection to try to reduce progressively the amount of involved data.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Breaking testcase
Excerpt of functions not triggering the error.
Trunk of htmlunit at Revision 3797 including Patch from #2318054
This seems to be a scope problem. Are you sure that you use the latest snapshot of core-js?
It would really help if you could reduce the problem (testing with web.de currently means 151.68 KB!). If you want to start looking at it with a debugger, a first step would be to verify the scopes of the Function objects involved when the exception arise. Additionally you can use the FalsifyingWebConnection to try to reduce progressively the amount of involved data.
Fixed in SVN. Thanks for the bug report, even though you weren't able to narrow it down ;-)
Thanks a lot Daniel, i tried to isolate the cause, but couldn't either.