Comment 50 for bug 1748450

Daniel van Vugt (vanvugt) wrote :

It appears that in the recent past this crash became so prolific that it might have been confused for other similar crashes in day to day bug maintenance. For example, the link

is actually a different crash with a different log message, and is not this bug at all. That has now moved to bug 1736664. Although the problem isn't just human error, but also I suspect there might be some automatic misclassification going on within too.

If you are experiencing bug 1736664 then please comment there. Otherwise please log new bug reports for each new crash you see so we can try to classify them better in future.