-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[instrumentation] "Object (...) should not be materialized" errors #1445
Comments
Do you have |
Good catch, yes I do. Apart from removing it, is there any other way to work around this problem? |
I'm afraid that's the only way to fix this problem currently, since the |
Thanks for the info! |
@fniephaus you may still use CompilerDirectives.ensureVirtualized in unit tests, maybe even use instrumentation to insert the check. |
@chumer I realized that |
When using the Chrome debugger via the
--inspect
option, we see quite a few compiler errors (such as the one below) for our language. It seems that the compiler is unable to optimize a call target due to aFrame#materialize()
call. How can this be fixed?The text was updated successfully, but these errors were encountered: