Bugzilla

(In reply to Haik Aftandilian [:haik] from comment #17)

> I just hit a crash that looks similar and immediately after restarting the crashing tab, I got the page telling me I need to restart the browser. I wonder if this is similar to the crashes fixed by bug 1366808 and if we need a similar fix for the RDD process. The issue bug 1366808 fixed was that the child process executable can be updated while the browser is still running and then when the parent launches a new child process, it has a different build ID compared to the long running parent process.

I see we do have the call to channel->SendBuildIDsMatchMessage() in RDDParent::Init() to check for build ID mismatches. But this was the first time I've hit the RDD crash and also very rarely see the page prompting me to restart the browser due to build ID mismatches. So I wonder if the crashes relate to updates.

(In reply to Haik Aftandilian [:haik] from comment #17)

> I just hit a crash that looks similar and immediately after restarting the crashing tab, I got the page telling me I need to restart the browser. I wonder if this is similar to the crashes fixed by bug 1366808 and if we need a similar fix for the RDD process. The issue bug 1366808 fixed was that the child process executable can be updated while the browser is still running and then when the parent launches a new child process, it has a different build ID compared to the long running parent process.

I see we do have the call to channel->SendBuildIDsMatchMessage() in RDDParent::Init() to check for build ID mismatches. But this was the first time I've hit the RDD crash and also very rarely see the page prompting me to restart the browser due to build ID mismatches. So I wonder if the crashes relate to updates.

My crash (apparently with an erroneous top stack frame) is crash report [d81ecd2c-0646-4dcc-9449-94f0f0190415](https://crash-stats.mozilla.org/report/index/d81ecd2c-0646-4dcc-9449-94f0f0190415)