Comment #32 on issue 27276 by [email protected]: PDF Re-entry Failure http://code.google.com/p/chromium/issues/detail?id=27276
Is it failing consistently for you? Does it work by refreshing the page after the failure? I just tried it ever 50 times and it didn't fail. However, I saw it failing at some point before (just once). The fix at r33412 still allows for sporadic failures when we are just unable to restart the request (for example the conditions for bug 28850, comment #9). However, the page should load properly by refreshing it after the error. So I'm personally OK with leaving this issue closed as long as the failure is not systematic, or at least lower the priority and punt it to Mstone-5 (some refactoring scheduled for that time frame _may_ allow us to remove some of the cases where we cannot restart the request) By the way, the problem is not really related with byte-range support for PDFs (as a feature), the issue is the support to resume truncated requests. -- 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
