Bug 1925926 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by

Nika Layzell [:nika] (ni? for response)

on 2024-10-23 10:15:04 PDT

This code is firing because the pid we got from the content process appears to conflict with the pid we got from the process launching code. I unfortunately don't have any ideas right now how we got into this situation.

Revision 1 by

Nika Layzell [:nika] (ni? for response)

on 2024-10-23 10:16:23 PDT

This code is firing because the pid we got from the content process appears to conflict with the pid we got from the process launching code. I unfortunately don't have any ideas right now how we got into this situation.
One possibility is that somehow the `GetProcId` call from earlier is failing (https://searchfox.org/mozilla-central/rev/360b702e1ec793c49dc66122e50fe580d43350b3/ipc/chromium/src/base/process_util_win.cc#94-106), and we're ending up with a `0` which is not `kInvalidProcessId` on windows, and falling over. Perhaps we can add an assertion that the pid is not `0` which is passed in.