On 2016/07/05 19:01, Dimitris Papastamos wrote: > On Tue, Jul 05, 2016 at 02:14:57PM +0200, Martin Pieuchot wrote: > > Without more information it's hard to find what could be the reason > > for this crash. Being able to reproduce the crash easily is the key > > to debugging. Can you do that? > > while :; do (chrome &); sleep 8; pkill chrome; done
Just a thought and I'm not sure whether it's worth anything or not, but when you get into ddb, it might be worth doing a ps and get the tid of chrome processes then doing 'tr /p 0t1234' (where the id is 1234; 0t forces decimal). At least this might throw some light on which syscalls have been invoked recently.
