Skip to content

Rendering is not threadsafe, corrupts global Node state #30

@jamadden

Description

@jamadden

The renderer wants to mix-in its own class (self.renderableClass) to the global Node class while it executes. When it is done, it wants to unmix them.

If all renderers in a process use the same renderableClass (generally they do), this is mostly not a problem, except when it comes to unmixing them; if another render is in progress when that happens, then it will blow up.

This could be solved by doing the mixing statically. However, we have a private renderer subclass that uses a different renderableClass, so that won't work. There are comments about setting up a proxy in the source code. What are other options/approaches?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions