Errors caused by destroying a stream #143
Description
I believe the two following errors are actually caused by the behavior of compress-commons.
- zip.entry callback never called when stream destroyed node-zip-stream#166
- ZipStream will keep writing to the readable side after destroy node-zip-stream#167
It seems that destroying a zip-stream is not 100% supported internally, causing memory leaks and lots of errors.