New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better error handling for gzip exceptions #447

Closed
chrisbcn opened this Issue Sep 20, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@chrisbcn

chrisbcn commented Sep 20, 2015

IMPORTANT: Please try to describe how did it happen.


App v.2.4.2-d618096
Source UID: 87446

Error: invalid stored block lengths
    at Zlib._handle.onerror (zlib.js:345:17)

@petrbrzek petrbrzek self-assigned this Oct 23, 2015

@petrbrzek

This comment has been minimized.

Show comment
Hide comment
@petrbrzek

petrbrzek Oct 23, 2015

Member

Thanks for your report. Does this error happen regularly or rather rarely? We definitely have to handle this error better.

Member

petrbrzek commented Oct 23, 2015

Thanks for your report. Does this error happen regularly or rather rarely? We definitely have to handle this error better.

@petrbrzek petrbrzek changed the title from crash report to Better error handling for gzip exceptions Oct 23, 2015

@rychlis rychlis referenced this issue Nov 16, 2015

Closed

bug #525

@jankuca jankuca referenced this issue Nov 30, 2015

Closed

( #546

@jakubzitny jakubzitny referenced this issue Dec 17, 2015

Closed

Error #570

@rychlis

This comment has been minimized.

Show comment
Hide comment
@rychlis

rychlis Jan 26, 2016

Member

Another related error:

Error: incorrect header check
    at Zlib._handle.onerror (zlib.js:345:17)

This error seems to be happening randomly, probably when the App downloads a corrupted resource due to networking issues

Member

rychlis commented Jan 26, 2016

Another related error:

Error: incorrect header check
    at Zlib._handle.onerror (zlib.js:345:17)

This error seems to be happening randomly, probably when the App downloads a corrupted resource due to networking issues

@petrbrzek

This comment has been minimized.

Show comment
Hide comment
@petrbrzek

petrbrzek Feb 5, 2016

Member

This error should be now fixed with the latest Avocode 2.5.3. Please try it and let us know.

Member

petrbrzek commented Feb 5, 2016

This error should be now fixed with the latest Avocode 2.5.3. Please try it and let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment