If gecko with bluetooth enabled starts up after bluetooth has already come up, then turning bluetooth off causes a request that makes the watch manager try to remove a socket that doesn't exist, crashing the browser.

Comment on attachment 622166 [details] [diff] [review] Fix crash due to lack of index check on watch sockets Review of attachment 622166 [details] [diff] [review]: ----------------------------------------------------------------- ::: ipc/dbus/DBusThread.cpp @@ +311,5 @@ > + // There are times where removes can be requested for watches that > + // haven't been added, so check to make sure we're using the watch > + // in the first place > + if(index >= 0) > + { if (index < 0) return; Also an example of when this might happen would be nice.