You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to nod...@googlegroups.com
At what point is it safe to reuse a buffer that is submitted to fs.write? Clearly when the callback is executed, but the buffer appears to be free on nextTick as well...
Kevin
Isaac Schlueter
unread,
Oct 9, 2012, 2:57:06 PM10/9/12
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to nod...@googlegroups.com
It is not safe to re-use a buffer once it's passed to an async method,
and before the callback. In the case of stream.write() it's not safe
to assume that it's *ever* ok to re-use it.
Memory is cheap. If you don't know for sure that it's your
bottleneck, just let it go out of scope and get collected.