(Moving it to inspector for triage.) I can't reproduce the issue with the provided STRs, but it's not that surprising. For the record we have several other bugs similar to this: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=mutation%20actor&list_id=15309219 The inspector walker actor maintains the list of known nodes on the server, in order to know which mutations need to be sent to the client. But this code can be racy / buggy. Mutations are queued so it's pretty easy to queue a mutation for a node which will be destroyed in the meantime. Honestly I think calling for bug filing in the warning message is too much, as most of the time we can't consistently reproduce the issues: ``` console.warn( "Got a mutation for an unexpected actor: " + targetID + ", please file a bug on bugzilla.mozilla.org!" ); ``` https://searchfox.org/mozilla-central/rev/a87a1c3b543475276e6d57a7a80cb02f3e42b6ed/devtools/client/fronts/walker.js#282 I suggest repurposing the bug in order to modify the error message, considering that those bugs are not actionable 99% of the time.
Bug 1644714 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(Moving it to inspector for triage.) I can't reproduce the issue with the provided STRs, but it's not that surprising. For the record we have several other bugs similar to this: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=mutation%20actor&list_id=15309219 The inspector walker actor maintains the list of known nodes on the server, in order to know which mutations need to be sent to the client. But this code can be racy / buggy. Mutations are queued so it's pretty easy to queue a mutation for a node which will be destroyed in the meantime. Honestly I think calling for bug filing in the warning message is too much, as most of the time we can't consistently reproduce the issues: ```javascript console.warn( "Got a mutation for an unexpected actor: " + targetID + ", please file a bug on bugzilla.mozilla.org!" ); ``` https://searchfox.org/mozilla-central/rev/a87a1c3b543475276e6d57a7a80cb02f3e42b6ed/devtools/client/fronts/walker.js#282 I suggest repurposing the bug in order to modify the error message, considering that those bugs are not actionable 99% of the time.
(Moving it to inspector for triage.) I can't reproduce the issue with the provided STRs, but it's not that surprising. For the record we have several other bugs similar to this: https://bugzilla.mozilla.org/buglist.cgi?quicksearch=mutation%20actor&list_id=15309219 The inspector walker actor maintains the list of known nodes on the server, in order to know which mutations need to be sent to the client. But this code can be racy / buggy. Mutations are queued so it's pretty easy to queue a mutation for a node which will be destroyed in the meantime. Honestly I think calling for bug filing in the warning message is too much, as most of the time we can't consistently reproduce the issues: ```javascript console.warn( "Got a mutation for an unexpected actor: " + targetID + ", please file a bug on bugzilla.mozilla.org!" ); ``` https://searchfox.org/mozilla-central/rev/a87a1c3b543475276e6d57a7a80cb02f3e42b6ed/devtools/client/fronts/walker.js#282 I suggest repurposing the bug in order to modify the error message, considering that those bugs are not actionable 99% of the time.