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

2.11.0 memory leak #33

Open
paleite opened this issue May 16, 2017 · 2 comments
Open

2.11.0 memory leak #33

paleite opened this issue May 16, 2017 · 2 comments
Labels

Comments

@paleite
Copy link

paleite commented May 16, 2017

2.10.0 worked without a problem, but 2.11.0 seems to be leaking memory.
Large projects can't allocate enough memory, but it works for smaller projects.

@balupton
Copy link
Member

that's strange, as the only change was an upgrade of taskgroup and extendr

taskgroup v5 should be a huge memory and performance win, which makes this strange - however, DocPad does not use it yet - the next minor version will

can you continue looking into this and post back your findings as you go - as I do not currently have the time to

@paleite
Copy link
Author

paleite commented May 18, 2017

If you look at 71d0d54#diff-f720b381cf00d86a4b6cbad9f5e642c5 you can see that there's been a change in the source, too.

If I'm not mistaken, the logic is different when obj = true, but I don't know if that's on purpose or not.

@mikeumus mikeumus added the bug label May 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants