3 ms·
What? You expect the VSCode maintainers to write up a lengthy explanation for why they have to mark every one of their 100k closed issues as closed? Are we real
by johnfn 6y ago
What? You expect the VSCode maintainers to write up a lengthy explanation for why they have to mark every one of their 100k closed issues as closed? Are we really ascribing malice because they didn't do that once?
C'mon, can't we be above this sort of behavior?
- basicneo 6y ago+1. It's reasonable for projects with large backlogs to do a quick prune with lower quality, either via manually or via tooling. If something is particularly pressing, it will re-appear. It's not ideal, but neither is a large backlog.
- hajile 6y agoThey didn't even ask for more details. They obviously didn't attempt to reproduce anything. They just closed the issue. The person who filed later noted that identical electron versions in earlier VS Code editions do not have the same problem. This doesn't appear to be a tiny issue either. It is leaking quite a bit of memory rather quickly. They need to find where they're retaining references in one version, but not the other (that kind of thing is what MS pays them for).