In fact I thought Chrome would never crash when one of the tab got screwed since there was this concept of each tab executing within a different process. A behaviour easily verified by browsing to about:memory and cross checking the PID with the windows process ID.
Sadly this near perfect browser crashed today :(
Should have noted down the steps that caused this. Have now enabled chrome to generate crash dumps as detailed here
No comments:
Post a Comment