search

samccone / drool

Automated memory leak detection and analysis
1.48k stars 53 forks source link

Input typing test #3

Closed tenbits closed 9 years ago

tenbits commented 9 years ago

Hello Sam,

adding here the tests with leaking nodes. The cause seems to be the initial input typing and typing after the input.value setter.

It looks like Chromes issue, what do you think?

samccone commented 9 years ago

Hi @tenbits thanks for following up and creating this test case, this is extremely odd. It is my understanding that once the page has loaded and executed JS (binding the event listeners) there should be 0 leaks with this example, however this test case seems to be in direct opposition. This will require a fair bit of more research to quantify this and hypothesize as to the cause.

tenbits commented 9 years ago

Hi Sam, I have recorded the heap snapshots before and after the test loop - leaky/input_investigation/test. But still no clue. Perhaps you can find smth out. Cheers, Alex

samccone commented 9 years ago

Hey @tenbits thanks for following up again, I shall take a look at the snapshots thanks!

samccone commented 9 years ago

@tenbits I have reduced the test case even more and have filed a bug over in chrome land https://code.google.com/p/chromium/issues/detail?id=516153&thanks=516153&ts=1438442933

Hopefully we will get a response :palm_tree: https://github.com/samccone/drool/commit/c0d264cc60052da669440f4dc7292cdd08bfa7a4

samccone commented 9 years ago

Since this is a chromebug, I will just close this for now. When I get the email that it has been resolved we can merge it in :)

tenbits commented 9 years ago

Sure ;)