3 ms·

You 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 ago
  It's not probably anymore, you're too late. See the message below. And no, 800 bytes is not a serious matter.
  - mihaigalos 4y ago
    I 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 ago
      I'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 ago
      Ahhh, if only Electron or Chrome shared that sentiment =)
      - mihaigalos 4y ago
        Electron or Chrome are not the topic of this thread. I also don't appreciate whataboutism, sorry.
  - the_duke 4y ago
    This type of hostile response to a very valid question is why you are not changing the opinion of many users here on HN. A leak is a valid concern, because it implies problems with memory management. "We choose to not free some memory on purpose" can be a valid explanation , but needs more context. You could be more persuasive by linking to the relevant code and explaining what memory it is and why you are leaking it. Otherwise your responses just seem like deflection.
    - amedvednikov 4y ago
      I'm sorry but this is the truth. This is completely irrelevant. Each V program uses an extra 800 bytes. If you look at what actual performance and low resource usage V brings to the table, you'll see it's not a problem at all.
      - the_duke 4y ago
        Well... I tried!
        amedvednikov 4y ago
        Since it seems to be important to many people here, I'll make sure valgrind reports 0 bytes :)
        the_duke 4y ago
        You are missing my point! My post wasn't about this concrete issue, which can also be explained. My point is about a civil discourse culture driven by (precise) technical arguments,not hostility or deflection. Which I am not seeing, which is why you only increase the skepticism here rather than change minds. Unless the leak was actually unintended and is a bug. But that's also fine, any language (old or new) has heaps of bugs in all corners of the codebase. But then just own up, explain and fix it.
        johnfn 4y ago
_gabe_ 4y ago
Why is this a nothingburger? If you're making the claim that it's safe and it actively leaks memory, how do we know it doesn't also allow buffer overruns or double frees? It would be nice if you allowed an option to compile with memory tracking so that as a user of the language you can debug this sort of stuff to make sure it's not a big deal waiting to happen.
- amedvednikov 4y ago
  800 bytes in some GC cleanup is not "actively leaking memory". It's a nothingburger. We know it's not a big deal, we have lots of valgrind tests running on CI. And we have V web services running for months and not leaking memory.

"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 ago
It's not probably anymore, you're too late. See the message below. And no, 800 bytes is not a serious matter.
- mihaigalos 4y ago
  I 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 ago
    I'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 ago
    Ahhh, if only Electron or Chrome shared that sentiment =)
    - mihaigalos 4y ago
      Electron or Chrome are not the topic of this thread. I also don't appreciate whataboutism, sorry.
- the_duke 4y ago
  This type of hostile response to a very valid question is why you are not changing the opinion of many users here on HN. A leak is a valid concern, because it implies problems with memory management. "We choose to not free some memory on purpose" can be a valid explanation , but needs more context. You could be more persuasive by linking to the relevant code and explaining what memory it is and why you are leaking it. Otherwise your responses just seem like deflection.
  - amedvednikov 4y ago
    I'm sorry but this is the truth. This is completely irrelevant. Each V program uses an extra 800 bytes. If you look at what actual performance and low resource usage V brings to the table, you'll see it's not a problem at all.
    - the_duke 4y ago
      Well... I tried!
      - amedvednikov 4y ago
        Since it seems to be important to many people here, I'll make sure valgrind reports 0 bytes :)
        the_duke 4y ago
        You are missing my point! My post wasn't about this concrete issue, which can also be explained. My point is about a civil discourse culture driven by (precise) technical arguments,not hostility or deflection. Which I am not seeing, which is why you only increase the skepticism here rather than change minds. Unless the leak was actually unintended and is a bug. But that's also fine, any language (old or new) has heaps of bugs in all corners of the codebase. But then just own up, explain and fix it.
        johnfn 4y ago

_gabe_ 4y ago

Why is this a nothingburger? If you're making the claim that it's safe and it actively leaks memory, how do we know it doesn't also allow buffer overruns or double frees? It would be nice if you allowed an option to compile with memory tracking so that as a user of the language you can debug this sort of stuff to make sure it's not a big deal waiting to happen.

amedvednikov 4y ago
800 bytes in some GC cleanup is not "actively leaking memory". It's a nothingburger. We know it's not a big deal, we have lots of valgrind tests running on CI. And we have V web services running for months and not leaking memory.