4 ms·
I find it funny that as soon as you [0] asked someone to list these major bugs in V especially when it turned out that they haven't used the language, they begi
by rvz 4y ago
I find it funny that as soon as you [0] asked someone to list these major bugs in V especially when it turned out that they haven't used the language, they begin to continue their regular deflection and dodging of the question.
It is a pattern I keep seeing here on HN, but its great that V hasn't given up and it is still active and maintained. No idea why this post was flagged.
[0] https://news.ycombinator.com/item?id=31943383 https://news.ycombinator.com/item?id=31943383
- forgotpwd16 4y agoWanna know something funnier also posted in previous thread? The hello_world.v has potential memory leaks. I tried it myself and got a similar result. Somehow the creator cannot reproduce this. ==57519== LEAK SUMMARY: ==57519== definitely lost: 0 bytes in 0 blocks ==57519== indirectly lost: 0 bytes in 0 blocks ==57519== possibly lost: 816 bytes in 3 blocks ==57519== still reachable: 0 bytes in 0 blocks ==57519== suppressed: 0 bytes in 0 blocks [1]: https://news.ycombinator.com/item?id=31931083 https://news.ycombinator.com/item?id=31931083 edit: Got something even better. $ valgrind --leak-check=yes v examples/hello_world.v ... ==58037== LEAK SUMMARY: ==58037== definitely lost: 4,463,772 bytes in 106,561 blocks ==58037== indirectly lost: 5,275,772 bytes in 84,005 blocks ==58037== possibly lost: 0 bytes in 0 blocks ==58037== still reachable: 47,149 bytes in 263 blocks ==58037== suppressed: 0 bytes in 0 blocks ...
- judge2020 4y agoReproduces on GitHub Actions: https://github.com/judge2020/test-v/runs/7150691976?check_suite_focus=true#step:4:11 https://github.com/judge2020/test-v/runs/7150691976?check_su...
- amedvednikov 4y agoLike I thought, this is some minor GC overhead. Wouldn't be there with `v -gc none hello_world.v`.
- amedvednikov 4y agoYou can stop spamming this nothingburger. 816 bytes is probably due to some GC overhead. It's nothing.
- forgotpwd16 4y ago"Probably" doesn't cut it if someone is going to user your language. Let's agree that this isn't a serious matter though. The compiler leaking is nothing as well?
- amedvednikov 4y agoIt's not probably anymore, you're too late. See the message below. And no, 800 bytes is not a serious matter.
- mihaigalos 4y agoI do think V is amazing and has a bright future. Thank you for putting time in it. If I may, I still believe even 1 byte is a serious matter imho.
- amedvednikov 4y agoI'd agree if it was happening in a loop somewhere. And a long running web service would leak memory over time. This doesn't happen, we have V web services running for months without leaks. But since there were several responses with this message, I'll make sure valgrind reports 0 :)
- gompertz 4y agoAhhh, if only Electron or Chrome shared that sentiment =)
- mihaigalos 4y agoElectron or Chrome are not the topic of this thread. I also don't appreciate whataboutism, sorry.
- mayama 4y agoI checked with valgrind too and see similar memory leaks. Is v compiler written in vlang yet? I see lot of warnings and leaks for the compiler.
- amedvednikov 4y agoIt has been written in V from the start (the first public release). V doesn't free memory when building V for performance reasons. A compiler is a perfect example of an app where freeing memory is totally fine on exit, by the OS. Fortunately V is efficient and doesn't result in gigabytes of RAM used when compiling large bases of code (V itself is about 110k loc + 100k of vlib). Once there are code bases that require gigabytes of RAM, we'll add an option to free it as it goes.
- amedvednikov 4y agoYeah it's a common pattern :)