| 2012-11-15 15:18:14 |
Matthew Paul Thomas |
description |
Launchpad querying being done asynchronously on errors.u.c means that the table of frequent crashes is updated in the background after the page loads. If you select a different release to view errors for while this thread is still running in the background, the thread is not cancelled. As a result, two different threads will be running to query launchpad data, for two different sets of crashes, and there's a race to see which one completes first. (And even if the race finishes in the right order, this results in excessive wibbling of the table since it will refresh twice, once with wrong data and once with the data you asked for.)
We somehow need these asynchronous lp queries to be cancelled when they are no longer relevant to what the user has requested. |
Launchpad querying being done asynchronously on errors.u.c means that the table of frequent crashes is updated in the background after the page loads. If you select a different release to view errors for while this thread is still running in the background, the thread is not cancelled. As a result, two different threads will be running to query launchpad data, for two different sets of crashes, and there's a race to see which one completes first. (And even if the race finishes in the right order, this results in excessive wibbling of the table since it will refresh twice, once with wrong data and once with the data you asked for.)
We somehow need these asynchronous lp queries to be cancelled when they are no longer relevant to what the user has requested.
It may save time to fix bug 1040140 at the same time as this bug. |
|
