1071795 - Firefox crashes when quitting while testing OMTC on Linux

Status: UNCONFIRMED

(Core :: Graphics, defect)

Description

[Jan Corazza]

Attachment: firefox output

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0
Build ID: 20140830210550

Steps to reproduce:

1. about:config
2. set layers.offmainthreadcomposition.enabled to true
3. set layers.acceleration.force-enabled to true
4. `export MOZ_USE_OMTC=1`
5. `firefox`

Steps 1 and 2 don't cause the bug, but the only enable the functionality. Without the 4th step - FF will run without OMTC, and without bugs.


Actual results:

Firefox starts normally, with a minor graphical glitch (half the screen is black for a second). Then it runs as expected with the same debug output as when started without the 4th line (`export MOZ_USE_OMTC=1` before launching `firefox` through the same terminal).

However, when quitting (by pressing the X button, or Ctrl+Q), the crash reporting window launches, and the executable prints this as its error (without "```" lines):

```
###!!! [Child][DispatchAsyncMessage] Error: Route error: message sent to unknown actor ID


###!!! [Child][DispatchAsyncMessage] Error: Route error: message sent to unknown actor ID
```

Full output is attached.


Expected results:

Firefox should have quit normally, without any extra terminal output, like when not using `export MOZ_USE_OMTC=1`.

Comment 1

[Jan Corazza]

This also happens in Nightly version "35.0a1 (2014-09-23)".

Comment 2

[Matthias Versen [:Matti]]

>the crash reporting window launches
Please provide the crash ID from about:crashes

Comment 3

[Jan Corazza]

I've recreated and re-submitted it, because I've reinstalled Firefox in the meantime, which got rid of the about:crashes list.

Bug ID: bp-22474ba3-38a8-4de6-9d7b-a74022140924
URL: https://crash-stats.mozilla.com/report/index/22474ba3-38a8-4de6-9d7b-a74022140924

Everything went on the same as it did before.

Comment 4

[Matthias Versen [:Matti]]

Your radeon driver crashes...

Comment 5

[Jan Corazza]

I didn't really experience any other effects. Other software didn't crash and continued to be properly accelerated.

I will test it with the  proprietary AMD Catalyst driver (fglrx).

But I still believe it's caused by Firefox because no other software has similar crashes.