Comment 27 for bug 1394424

I see. I thought there might be new or different information since this occurred without without the boot parameters you asked about.

It's more difficult to trigger the bug now, so something has changed. I used to reload the crashed Chromium session and since the page that caused the crash would be reloaded, it would occur again as soon as the page loaded. However, I've just rebooted and restarted Chromium with the pages that caused the crash and everything works fine. It's kind of random now; I thought it had been fixed in a recent update that included some intel/vesa packages, but I guess not.

Let me know if you need me to check anything else. Thanks for your help.