User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 Build ID: 20160802030437 Steps to reproduce: - Go to a a trello.com board - open a card - close a card - do stuff Actual results: The board is flickering. Expected results: No flickering.
Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 I have tested this issue on Ubuntu 16.04 x64 with the latest Firefox release (48.0) and the latest Nightly (51.0a1-20160807030201) and could not reproduce it. After navigating to trello.com. I have created different boards, changed their color, opened new lists, added cards, added labels, dragged cards from a list to another, edit them, closed them, switched between boards but I haven't encountered any flickering. Can you please retest this using a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E).
I tested it on safe mode. Ubuntu 14.04 x64 Firefox 51.0a1. It is not automatic but it appends a lot when I'm closing or moving a card. My board is pretty active (11 columns and a lot of cards). Trello is always heavy on Firefox anyway if you compare it with to Chromium.
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 I have retested this issue on Ubuntu 14.04 with the latest Firefox release (48.0.1) and still could not reproduce it. However, using the latest Nightly (51.0a1-20160824030337), I've managed to reproduce it and performed a regression. After logging in to trello.com, when dragging a card from a column to another column, you can observe that the column and sometimes the hole window is flickering. Here are the regression results: Last good revision: 14733a383b4cf29ce6ed70a5d22dd3cb060c0eb1 First bad revision: afd27635d16ebe223b9186f0033b77cd2bbb48d5 Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=14733a383b4cf29ce6ed70a5d22dd3cb060c0eb1&tochange=afd27635d16ebe223b9186f0033b77cd2bbb48d5
Status: UNCONFIRMED → NEW
Component: Untriaged → Graphics
Ever confirmed: true
Product: Firefox → Core
Bug 594876 looks suspect in that range. acomminos, does anything in here sound related to layers acceleration on Linux?
It's possible- what kind of flickering is being seen here? Appearance and disappearance of the cards, tearing, or something else? If you could provide the contents of the 'Graphics' section of your about:support, that would be immensely helpful as well.
Flags: needinfo?(andrew) → needinfo?(emil.pasca)
To me, it's more like appearance and disappearance and slow reaction. My 'Graphics' section: Graphics Features Compositing OpenGL Asynchronous Pan/Zoom wheel input enabled; touch input enabled WebGL Renderer Intel Open Source Technology Center -- Mesa DRI Intel(R) Haswell Mobile WebGL2 Renderer WebGL creation failed: * WebGL 2 requires support for the following features: transform_feedback2 * Exhausted GL driver options. Hardware H264 Decoding No Audio Backend pulse GPU #1 Active Yes Description Intel Open Source Technology Center -- Mesa DRI Intel(R) Haswell Mobile Vendor ID Intel Open Source Technology Center Device ID Mesa DRI Intel(R) Haswell Mobile Driver Version 3.0 Mesa 10.1.3 Diagnostics AzureCanvasAccelerated 0 AzureCanvasBackend skia AzureContentBackend skia AzureFallbackCanvasBackend none CairoUseXRender 0
Created attachment 8788186 [details] trello_issue.gif Graphics Features Compositing OpenGL Asynchronous Pan/Zoom wheel input enabled; touch input enabled WebGL Renderer ATI Technologies Inc. -- AMD Radeon (TM) R7 300 Series WebGL2 Renderer ATI Technologies Inc. -- AMD Radeon (TM) R7 300 Series Hardware H264 Decoding No; Failed to create H264 decoder Audio Backend pulse GPU #1 Active Yes Description ATI Technologies Inc. -- AMD Radeon (TM) R7 300 Series Vendor ID ATI Technologies Inc. Device ID AMD Radeon (TM) R7 300 Series Driver Version 4.4.13374 Compatibility Profile Context 15.20.1013 Diagnostics AzureCanvasAccelerated 0 AzureCanvasBackend skia AzureContentBackend cairo AzureFallbackCanvasBackend none CairoUseXRender 0
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.