https://bugs.kde.org/show_bug.cgi?id=397834
--- Comment #23 from Martin Stransky <stran...@redhat.com> --- (In reply to David Edmundson from comment #20) > We seem to end up in the code path where Firefox doesn't have a buffer > available and waits. However FF should be coping with that state. Something > it'd be good for Martin S to check. I can patch Firefox to use more buffers if that helps you. Also Firefox draws to wayland in an extra thread (compositor thread), the wl_surfaces/buffers are created/attached there...maybe the event loop at compositor thread is wrongly configured/handled, events are not propagated between Firefox compositor thread and Wayland compositor thus the buffers are not released/attached? -- You are receiving this mail because: You are watching all bug changes.
