Comment #4 on issue 9151 by [email protected]: google search results jumbled http://code.google.com/p/chromium/issues/detail?id=9151
This is an SDCH corruption (i.e., browser requested SDCH compression, server provided SDCH compression, but decoding did not take place). The typical cause of this corruption is that proxy (or AV software) stripped the content-encoding, and then (for some reason) the error recovery code in Chrome did not "recover" gracefully. You can tell it is SDCH by the tell-tale first 9 bytes on the page, the first 8 of which are ASCII, and the 9th is a null. I also recognize the ASCII bytes as being the descriptor of a current experimental SDCH dictionary. Here are a few such (recent) dictionary IDs: REteF8DM IOMdKgnl v9EV8Xfd The critical point is that this is a base64 style coding of a hash. The legal characters include letters (upper and lower), digits, as well as a hyphen and underscore, for a total of 64 allowable characters. To help to better diagnose this problem. It would be VERY helpful if the user visited the Chrome link: about:histograms/Sdch and then cut/pasted the entire results into this bug (immediately after reproducing the bug as was described above). As a short-term work-around, the user can disable SDCH by adding teh command line switch: --enable-sdch=nothing Thanks in advance for your assistance, Jim -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
