Maximum amount of decompressed data reached, login fails

[Hawk777]

When I enable a Google Chat account in Pidgin, I get an http: Maximum amount of decompressed data is reached error in the debug window, and then it never enables. No error is shown in the main Pidgin window, but the icon in the Accounts window stays grey (though the checkbox is checked) and my contacts never appear.

purple-debug.log

[EionRobb]

I don't think I'm setting any max response sizes anywhere, so it's defaulting to 1MB. There must be something that's bigger than that going on somewhere. I'll try allowing up to 10MB and see if that helps

[EionRobb]

If you're able to update to the release after the above commit to see if that helped, that would be amazing :)

[Hawk777]

Interesting. That gets rid of the http: Maximum amount of decompressed data is reached and http: Maximum length exceeded, truncating lines, but the connection: Connection error on 0x5576b180dcc0 (reason: 0 description: Invalid response) failure is still there (with a different address, of course, but still in the same place in terms of the sequence of events), and the overall result is the same.

[EionRobb]

Hmm. That is strange!

Can I get a new debug log, pretty please? 🙂

[Hawk777]

Certainly!

purple-debug.log

[EionRobb]

That's really annoying :/ It's definitely progressing now, but who knows why it's dying.

Does this happen with a brand new Pidgin account, or is it happening for an existing setup in Pidgin? (I'm wondering if the old credentials might be expiring and we're not detecting that properly, or a failure in the new cookie credentials are not being verified by the plugin correctly)

[Hawk777]

Ah, is that an authentication-related HTTP request? It’s an old account that started doing this sometime recent-ish-ly (I’m not sure exactly when because the failure is, annoyingly, silent; unlike most protocol failures, it doesn’t show up in the main Pidgin window as an error message). If you think it’s worthwhile, and there’s nothing further you want to debug (e.g. dumping the failed request to a file and looking at it), I can try getting fresh cookies.

[Hawk777]

Oh, I finally got around to refreshing the cookies and now it seems to have logged in fine. I guess this can be considered low priority: the remaining bug is that, when something goes wrong, it should show the error panel in the Pidgin window, instead of failing silently.