Open Bug 1529575 Opened 5 years ago Updated 2 years ago

Investigate races between discardBrowser() and AsyncTabSwitcher.jsm

Categories

(Firefox :: Tabbed Browser, defect, P3)

Product:
Firefox
Component:
Tabbed Browser
Type:
defect

Tracking

()

People

(Reporter: gsvelto, Unassigned, NeedInfo)

References

(Blocks 2 open bugs)

Details

While manually testing the patch in bug 675539 I hit a race by unloading multiple tabs in a short amount of time while switching between them (note: the machine was under heavy load hence the UI was quite slow to respond).

Since I was quickly cycling through tabs I might have switched to a tab that was about to be unloaded, or maybe I just switched to a tab that had just been unloaded, I cannot be sure which. However I got an exception from AsyncTabSwitcher.jsm where the tab's frameLoader field was null. Unfortunately I haven't saved the log; I'll try to reproduce the problem and attach it here.

Blocks: async-tab-switcher, tab-unloading
Priority: -- → P3
Type: enhancement → defect

From an end user perspective (without looking at exceptions), what might be a symptom of this bug?

The tab remains empty even though it should either contain a page or reload one that was just unloaded.

Severity: normal → S3

The severity field for this bug is relatively low, S3. However, the bug has 43 votes.
:dao, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dao+bmo)
You need to log in before you can comment on or make changes to this bug.