Hi everyone, This is a quick note to remind you of the adverse effects of IPC messages that can be sent from the content process to the parent process especially from web content Javascript accessible APIs.
Let's say you have a JS callable function foo() which sends the IPC message MsgBar to the parent process for further processing each time it is called. This will make it possible for an abusive or poorly written page to spam the parent process with a lot of MsgBar messages if the page does something like: while (true) foo(); Such a page can interfere with the slow script notification being displayed and interacted with in the parent process, which is quite bad, and that problem may exacerbate the issue of the long running JS running in the content process as the user may be unable to stop it. This came up earlier today in https://bugzilla.mozilla.org/show_bug.cgi?id=1438214, and I decided to send a note about the problem so that people can consider coalescing such messages when the calls to foo() happen too frequently when writing new code. Thanks, -- Ehsan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform