-
Notifications
You must be signed in to change notification settings - Fork 178
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
int overflow errors on large buffers #22
Comments
I don't know that anybody contemplated using a single buffer for more than 2Gb of data: seems a bit extreme. We could code around the particular crash by avoiding the call to len(self.buf), e.g.:
|
2GB is not much when it comes to pushing large repos, (this is what user was doing i assume). Your fix wouldn't help i think because it crashes inside I wrote small test and a fix that looks like this:
I can open a PR if that would be accepted |
I found another case of this:
|
Is this with the current release (0.8.7)? Because 'outbuf' should be an instance of the OverflowableBuffer whose 'len' you helped fix earlier. Hmm, it does look like there is one case where a non-OB is added to 'self.outbufs': https://github.com/Pylons/waitress/blob/master/waitress/channel.py#L310 So, I guess we need to fix the ReadOnlyFileBasedBuffer too. But this should really be a new issue (or better, PR). |
I created new issue #47 |
Org traceback can be found here:
https://bitbucket.org/marcinkuzminski/rhodecode/issue/838
So basically python expects an int when it calls len(), it seems that buffer length can exceed that , and len functions on buffers can return more than that.
Seems to be hard to fix issue, not sure if that should be fixed even ?
The text was updated successfully, but these errors were encountered: