Status: Unconfirmed Owner: ---- Labels: OS-Linux Area-Misc Size-Medium Type-Bug
New issue 23262 by jlmjlm: Browser crash when kerberized NFS expires. http://code.google.com/p/chromium/issues/detail?id=23262 Chrome Version : 4.0.219.3 (Developer Build 27219) OS + version : ghardy CPU architecture (32-bit / 64-bit): 64-bit Opteron window manager : fvwm URLs (if applicable) : Behavior in Firefox 3.x (if applicable): No crash, continues to run properly after Kerberos is renewed. Behavior in Chrome for Windows (optional): What steps will reproduce the problem? 1. Start chrome with your home directory on Kerberized NFS. 2. Wait; do not renew Kerberos; let Kerberos credentials to your home directory expire. 3. Wait; leave chrome running, but don't interact with it. (2+3 can be accomplished by locking your workstation for the weekend and not logging in to it.) What is the expected result? Chrome continues to run after Kerberos is renewed. What happens instead? Chrome has crashed. Please provide any additional information below. Attach a screenshot and backtrace if possible. Console output, including backtrace, attached. Attachments: crerr2 53.6 KB -- 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 -~----------~----~----~----~------~----~------~--~---
