Comment 12 for bug 532652

Gary Lasker (gary-lasker) wrote :

There is a good chance that the current manifestation of this bug is in actuality one of either bug 688991 or bug 694836. These are our current "crashers" with duplicates for which the fix has not yet been released (the first is fix committed now and the second has a fix under review). The stacktrace will let us know for sure.

Thanks again!