Hi, Sorry I wasn't clear enough.
-The first time I experienced the bug I had libexif 0.6.20-3 installed and it was reproducible. -After you asked me to downgrade I installed libexif 0.6.20-2, the bug was still reproducible. -I was later asked to try to get a trace from gdb, I have never been able to get a trace of the bug because chromium kept crashing at start-up, the traces that I've sent are from those crashes. -Emmanuel pointed out that his browser was also experiencing those crashes at start-up with --single-process enabled. -I disabled all the plugins and executed chromium with and without --single-process, I haven't been able to reproduce it since then. The only way to make it crash is using gdb and --single-process (but it crashes at start-up which makes me think is something unrelated to this bug). I think the segfaults were something related to a plugin since I haven't been able to reproduce it since I disabled them. Eugenio On Sat, Aug 4, 2012 at 2:20 AM, Jonathan Nieder <jrnie...@gmail.com> wrote: > Hi, > > Eugenio Cano-Manuel Mendoza wrote: > > > I don't think libexif is the problem since this crashed occured with > > version 0.6.20-2 of the package... > > That's new information. So do I understand correctly that: > > - when you first experienced the bug, you had libexif 0.6.20-2 installed > and it was reproducible for a few days > > - when I asked you to try downgrading libexif, you did nothing, and, > typically for a Heisenbug, it stopped being reproducible > > - you had some extensions installed at both stages (which extensions?) > that you have now uninstalled > > Curious, > Jonathan >
