Comment #26 on issue 12189 by darthandroid: Renderer freezes http://code.google.com/p/chromium/issues/detail?id=12189
Does a workaround count as fixed? I've managed to make the problem go away thanks to comment #23, but this is not a default configuration and reappears as soon as I reverse the changes back to a default configuration, so the programmer part of me doesn't like calling this "fixed" when the bug still exists. Is there a "workaround- available" tag that would be better suited, or are there internal discussions of rewriting the proxy code and render this issue fixed in the process? Since I'm able to use chrome again, getting the bug fixed is far lower on my day-to-day list of priorities, but I'd still like to see it properly fixed for the sake of other users to whom I recommend chrome and most certainly have never heard of a 'proxy' in computer terms. -- 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
