Fix leak of data when streaming JPEG

[LinusU]

Fixes #773

[LinusU]

ping @rlidwka, would you mind reviewing/testing this for me? :)

I have verified that the image does indeed get smaller, and it's no longer a multiple of 4096. It can also open the image in the Preview app in OS X so it seems valid.

[LinusU]

@TooTallNate @kangax @rvagg @kkoopa @zbjornson

Any thoughts on how to handle this, we are leaking users memory, potentially in web apps which could be exploited.

I think that we should npm deprecate all the current versions with a message on what's happening and urging all users to update to a version that we'll publish when we merge this.

[zbjornson]

That sounds reasonable and responsible. By "all current versions" do you mean all 86 published versions?

Nice job getting a fix submitted quickly. 👍

[LinusU]

Published as 1.3.16

Would still appreciate input on how to move forward with the deprecation...

[kkoopa]

I guess whether to deprecate or not depends on how much JPEG streaming is used.