Skip to content
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

ascii85 can't decode what it encodes when the result is large #14

Open
michael-ts opened this issue Sep 28, 2018 · 4 comments
Open

ascii85 can't decode what it encodes when the result is large #14

michael-ts opened this issue Sep 28, 2018 · 4 comments

Comments

@michael-ts
Copy link

I've got a somewhat large binary input (3238814 bytes) that I tried to encode. It encodes fine, but when I try to decode it fails. I tried smaller inputs (<100k) and they all worked. The larger input encodes and decodes fine in the default encoding, but it's a bit of a pain to have to pad out to a multiple of four.

@altmind
Copy link

altmind commented Mar 18, 2019

Can confirm for z85, seem that encoding something along 100K is a browser yields an "undefined" as a encode result. 40K works fine.

@smurfix
Copy link
Contributor

smurfix commented Nov 12, 2024

Is this still an issue? I just tested with an 8MB string. In any case this seems like a JS runtime problem, not one of base85.

@noseglid
Copy link
Owner

noseglid commented Nov 18, 2024

Thanks for reporting! Can you please provide a dataset to use which exhibits the issue.

@noseglid noseglid reopened this Nov 18, 2024
@noseglid
Copy link
Owner

Ooops, wrong button

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants