On Mon, Jul 4, 2016 at 3:35 AM, mhhcbon <cpasmaboiteas...@gmail.com> wrote: > Hi, > > I have this program which reads file, flate encode then flate decode the > data. > > I noticed that when i used different size for the slice of []byte to read > data, the program will retain memory when the size is > 16384. > When its lower than this value everything is fine, but 16385 breaks. > > I don t quite understand the reason of this behavior, can someone help me to > understand what s going on there ?
I can't see anywhere that this program could be holding on to extra memory it's not using. But the problem might just be that you're writing many more bytes to your encoder than you're reading from the file. _, err := src.Read(b); // read from file Read() isn't required to fill the whole buffer it's given. It can read a single byte and return. Because you're ignoring the value telling you how many bytes it read you're passing the whole 16385 slice to your encoder even though you might have read much less than 16385 bytes. This means the size of buf2 could be much larger than the original file and also full of junk data from previous reads and zeroed bytes. Read() is a low level call that you should avoid calling directly because it's tricky to get right. For an example of how to properly call a Read() see the implementation of io.Copy() https://golang.org/src/io/io.go?#L366 -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
