memory/resource leak about weld HOT 7 CLOSED

cool, i'll add this to the test suite, thanks!

from weld.

I'm seeing a too many open files error (branch: pluggable, commit: 3a3468a)

from weld.

try increasing your maximum open files -- i tend to run fairly hot.

that said, the fact that you're hitting open file max tells me that something inside either weld or jsdom is opening files and not returning resources. unfortunately, i haven't had time to delve in to find it, if i manage to get more time this weekend, i will.

from weld.

emailed tmpvar a patch that eliminates the too many open files: allows script fragments instead of files for env().

memory leak still happening.

from weld.

hrm, I believe this is a jsdom issue

from weld.

looking at weld, and the fact that i was able to replicate the issue without weld, i am inclined to agree.

sorry, should have written an alternate test before opening a bug report.

will re-open over at jsdom with weld-free test.

@tmpvar - thoughts on including the patch i emailed into jsdom? could save a lot of i/o.

from weld.

+1 still an issue

from weld.