Since updating my browser to Firefox 35.0 last week, I've been getting bursts (dozens at a time) of identical error messages in my system log of the following character:

[0x0-0x7cd7cd].org.mozilla.firefox: ###!!! [Child][DispatchAsyncMessage] Error: (msgtype=0xAA0001,name=PTexture::Msg___delete__) Route error: message sent to unknown actor ID

Does anyone know what this means? Is it something to be concerned about (even though it doesn't seem affect Firefox's functioning)? Or is it just another 'insignificant' and annoying flaw in Firefox which will likely be fixed in the next iteration?

I am not able to provide any information other than it appears the error has been registered at Bugzilla as Bug 1078134.

Merci.

'Twould appear that the bug has been around for a while but has only affected the latest version of Firefox and probably will be dealt with sometime in near future.

As for Bugzilla: I long ago gave up on checking things there. The moderators seem to have little patience for those of us who can't get the hang of their reporting system and they can be downright rude about it. They also seem to think that all bug reporters should be conversant with all aspects of geekese and nerdese.

FYI — Mozilla just updated Firefox 35.0 to 35.0.1 with a whole whack of fixes.
Sad to say, this particular issue was not among them; the error messages continue to occur in 30-40 identical bursts.
So, the waiting game continues.

It just caught my eye that this bug was originally reported on 2014-10-06. There has been no apparent work done to clear the wayward warning since then, so it would seem unlikely that it'll be resolved in the next iteration or few. {sigh}

And it doesn't appear to have been addressed in Firefox 36.0, released yesterday.
In fact, no one concerned with the bug at Bugzilla appears to be interested enough to do anything about it.

I may have jumped the gun:
• There is no mention of the bug (fixed, unfixed or otherwise) in Firefox 36.0's Release Notes.
• The bug usually showed up when closing Firefox; it no longer does.
• The Bugzilla bug ticket hasn't been updated since its inception last October.

So, we shall have to wait and see if it rears its ugly head again.

It's been over a week and no sign of the bug.
So even though the bug ticket hasn't been updated, the problem seems to have been addressed.