Skip to content

Possibly leaking DOM node references #219

Closed
@kevinrobinson

Description

@kevinrobinson

I ran into this doing some profiling as part of kevinrobinson#1. It looks like there's a DOM leak somewhere.

You can see the test case I'm using here on the counters app:

screen shot 2015-07-05 at 10 00 23 pm

This might not matter much in real applications, and I'm not quite sure how to investigate further. I tried seeing if I could find more in the profiling tools but didn't get anywhere yet. I also read through the code to see if anything stuck out but couldn't see anything there either.

Maybe someone else knows more about profiling this, or can track it down?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions