Skip to content
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

Cleanup ComposeLayoutRenderers class init workaround #59

Closed
zach-klippenstein opened this issue Aug 22, 2020 · 1 comment
Closed

Cleanup ComposeLayoutRenderers class init workaround #59

zach-klippenstein opened this issue Aug 22, 2020 · 1 comment

Comments

@zach-klippenstein
Copy link
Collaborator

My response too. Doesn't happen normally, only happens when the debugger was connected and about to stop at a breakpoint that involved ViewStateRenderers.

The NoClassDef wasn't for compose, it was for this class, because of the circular ref. VSR starts initializing, asks this class for its defaults, this class starts initializing, which calls functions on VSR which require that class to be loaded, but it's already in the process of initializing.

I'm not sure why this wasn't happening unless the debugger was connected. Anyway a better solution might just be to make the VSR.Defaults* fields initialize lazily.

Originally posted by @zach-klippenstein in #33 (comment)

@zach-klippenstein
Copy link
Collaborator Author

This is obsolete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant