It looks like the issue might be that the StringBundle isn't initialized before an error occurs. But that only explains the second variant, not the first. I am not sure how the modules changes impacted the first. I'll ask around.
Bug 1806064 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
It looks like the issue might be that the StringBundle isn't initialized before an error occurs. But that only explains the second variant, not the first. I am not sure how the modules changes impacted the first, as that happens on the content process and not on the worker process or the main thread while doing worker work. I'll ask around.
It looks like the issue might be that the StringBundle isn't initialized before an error occurs. But that only explains the second variant, not the first. I am not sure how the worker modules changes impacted the first, as that happens on the content process and not on the worker process or the main thread while doing worker work. I'll ask around.
It looks like the issue might be that the StringBundle isn't initialized before an error occurs. But that only explains the second variant, not the first. I am not sure how the worker modules changes impacted the first, as that happens on the content process and not on the worker process or the main thread while doing worker work. In particular, it looks like an issue when opening PDF files. I'll ask around.
It looks like the issue might be that the StringBundle isn't initialized before an error occurs. But that only explains the second variant, not the first. I am not sure how the worker modules changes impacted the first, as that happens on the content process and not on the worker process or the main thread while doing worker work. In particular, it looks like an issue when opening PDF files -- which suggests that the pdf worker might be triggering it... but the error still comes from content. I'll ask around.