On Tue, Feb 24, 2015 at 04:45:37PM GMT, frantisek holop wrote: > with the Mesa rollback it is now possible > to run chromium again without --disable-gpu. > > however with or without, after exiting > there is always a core dump. i suspect > this has been the case for some versions now. > > anybody else is seeing this?
After I had enabled "2-step Verification", and hadn't re-logged onto Google services, it would generate a core dump every time I quit 'chromium'. Additionally, it would crash every time when I attempted to sign into my Google account as log as I had a Security Key (i.e. my Yubikey) *added* in my Google 2-step Verification settings. After removing it from there, but still with 2-step Verification enabled, it doesn't crash (and generate core dump) any more. I've just tested it with a clean profile (i.e. after 'rm -fr ~/.config/chromium ~/.cache/chromium') after logging onto Google services 'chromium' would dump the core every time I *start* it (i.e. from 'cwm' menu) - it would still run normally though. After a couple of start/quit cycles, it doesn't generate a core dump any more. Hmm... the only thing I can think of that would cause this (and the one with the older profile) was the data sync, i.e. now that it had synced the data, it doesn't dump the core any more, and earlier, it would dump the core on close because it couldn't synchronise the data back (i.e. me not being signed into Google services). However, this is just a speculation. Raf
