Open Bug 1534327 Opened 5 years ago Updated 8 days ago

Session store gets broken/oldest window is missing when Firefox is closed with a newly opened window

Categories

(Firefox :: Session Restore, defect, P3)

Product:
Firefox
Component:
Session Restore
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox67 --- affected

People

(Reporter: mayhemer, Unassigned)

References

(Blocks 1 open bug)

Details

Win10x64, currently Nightly, saving open windows.

STR:

I'm having an old session with 3 windows open, two monitors, many tabs, each window remembers its position, I always use sandwich menu -> Exit to close in one window I treat as "the main" because there are few pinned tabs

  • Run Fx
  • Open a new window, open few tabs in it; the result is there are now 4 windows open
  • Close Fx (as described above)
  • Open Fx again

AR:
The "main" window is gone, the new window remains (so, instead of 4 wins I have 3)

ER:
obviously, get the same as before closing Fx (4 windows)

This is somewhat consistent. Because of some HW trouble I turn off my dev machine every day. First this was encountered on Feb 3 and happened 3 times since then. Today the session was even broken (I got the "restore or new" window after start) and on clicking restore I got again this bug.

Backup in sessionrestore-backups/previous.jsonlz4 is correct; copying over the root sessionstore.jsonlz4 reverted the windows as expected for me.

Today I got an empty single window. There is really something wrong in session store lately.

Mike, please let me know who to cc/nag about this really very annoying bug, thanks.

In case this may help, this is what I can see in the browser console after restart with the oldest window missing (but I don't believe anything is actually relevant):

1553527467656	addons.webextension.{3923146e-98cb-472b-9c13-f6849d34d6b8}	WARN	Loading extension '{3923146e-98cb-472b-9c13-f6849d34d6b8}': Reading manifest: Error processing key: An unexpected property was found in the WebExtension manifest.
1553527467719	addons.webextension.treestyletab@piro.sakura.ne.jp	WARN	Loading extension 'treestyletab@piro.sakura.ne.jp': Reading manifest: Error processing variable_color_icons: An unexpected property was found in the WebExtension manifest.
TypeError: this.appMenuStatus is undefined
2 browser-sync.js:344:24
    updatePanelPopup chrome://browser/content/browser-sync.js:344
    updateAllUI chrome://browser/content/browser-sync.js:192
    maybeUpdateUIState chrome://browser/content/browser-sync.js:110
    showFxaToolbarMenu chrome://browser/content/browser.js:487
    onDOMContentLoaded chrome://browser/content/browser.js:1445
    onDOMContentLoaded self-hosted:985
[Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIContentSniffer.getMIMETypeFromContent]"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 230"  data: no]
    onStopRequest resource:///modules/FaviconLoader.jsm:230
    AsyncFunctionNext self-hosted:820
Error: WebExtension context not found! 5 ExtensionParent.jsm:1041:13
ReferenceError: title is not defined 2 ActiveSessionManager.js:414:7
Promise resolved after context unloaded
content.js:45
    <anonymous> moz-extension://d17fc4f5-54ff-40b4-820e-719d26080f18/content.js:45
ReferenceError: title is not defined ActiveSessionManager.js:414:7
Cannot send function call result: other side closed connection (call data: ({path:"storage.sync.get", args:[["optionsExpandedGroups", "sidebarScrollbarPosition", "faviconizePinnedTabs", "counterRole", "maxTreeLevel", "indentAutoShrink", "indentAutoShrinkOnlyForVisible", "labelOverflowStyle", "showContextualIdentitiesSelector", "showNewTabActionSelector", "longPressOnNewTabButton", "zoomable", "showCollapsedDescendantsByTooltip", "fakeContextMenu", "emulateDefaultContextMenu", "context_reloadTree", "context_reloadDescendants", "context_closeTree", "context_closeDescendants", "context_closeOthers", "context_collapseTree", "context_collapseAll", "context_expandTree", "context_expandAll", "context_bookmarkTree", "context_groupTabs", "context_closeTabOptions_closeTree", "context_closeTabOptions_closeDescendants", "context_closeTabOptions_closeOthers", "context_collapsed", "context_pinnedTab", "context_unpinnedTab", "shouldDetectClickOnIndentSpaces", "autoCollapseExpandSubtreeOnAttach", "autoCollapseExpandSubtreeOnSelect", "autoCollapseExpandSubtreeOnSelectExceptActiveTabRemove", "collapseExpandSubtreeByDblClick", "autoExpandIntelligently", "autoExpandOnCollapsedChildActive", "autoExpandOnTabSwitchingShortcuts", "autoExpandOnTabSwitchingShortcutsDelay", "autoExpandOnLongHover", "autoExpandOnLongHoverDelay", "autoExpandOnLongHoverRestoreIniitalState", "skipCollapsedTabsForTabSwitchingShortcuts", "parentTabBehaviorForChanges", "syncParentTabAndOpenerTab", "dropLinksOnTabBehavior", "showTabDragHandle", "tabDragBehavior", "tabDragBehaviorShift", "showTabDragBehaviorNotification", "fixupTreeOnTabVisibilityChanged", "autoGroupNewTabs", "autoGroupNewTabsTimeout", "autoGroupNewTabsDelayOnNewWindow", "autoGroupNewTabsFromPinned", "insertNewChildAt", "insertNewTabFromPinnedTabAt", "scrollToNewTabMode", "scrollLines", "autoAttach", "autoAttachOnOpenedWithOwner", "autoAttachOnNewTabCommand", "autoAttachOnNewTabButtonMiddleClick", "autoAttachOnDuplicated", "autoAttachSameSiteOrphan", "guessNewOrphanTabAsOpenedByNewTabCommand", "guessNewOrphanTabAsOpenedByNewTabCommandUrl", "inheritContextualIdentityToNewChildTab", "inheritContextualIdentityToSameSiteOrphan", "closeParentBehavior", "promoteFirstChildForClosedRoot", "moveTabsToBottomWhenDetachedFromClosedParent", "promoteAllChildrenWhenClosedParentIsLastChild", "moveFocusInTreeForClosedActiveTab", "successorTabControlLevel", "simulateSelectOwnerOnClose", "supportTabsMultiselect", "warnOnCloseTabs", "animation", "smoothScrollEnabled", "smoothScrollDuration", "burstDuration", "indentDuration", "collapseDuration", "outOfViewTabNotifyDuration", "tabDragHandleDelay", "tabDragHandleFeedbackDuration", "bookmarkTreeFolderName", "defaultBookmarkParentId", "defaultSearchEngine", "acceleratedTabOperations", "acceleratedTabCreation", "acceleratedTabDuplication", "enableWorkaroundForBug1409262", "simulateCloseTabByDblclick", "maximumAcceptableDelayForTabDuplication", "acceptableDelayForInternalFocusMoving", "notificationTimeout", "startDragTimeout", "longPressDuration", "moveDroppedTabToNewWindowForUnhandledDragEvent", "autoDiscardTabForUnexpectedFocus", "autoDiscardTabForUnexpectedFocusDelay", "knownExternalAddons", "useCachedTree", "simulateSVGContextFill", "applyThemeColorToIcon", "newTabAnimationDuration", "userStyleRules", "debug", "loggingQueries", "logFor", "importedConfigsFromLegacy", "legacyConfigsNextMigrationVersion", "configsVersion", "importedTreeStructureFromLegacy", "migrateLegacyTreeStructure"]]})) 3
[Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIContentSniffer.getMIMETypeFromContent]"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 230"  data: no]
    onStopRequest resource:///modules/FaviconLoader.jsm:230
    InterpretGeneratorResume self-hosted:1266
    AsyncFunctionNext self-hosted:820
ReferenceError: title is not defined ActiveSessionManager.js:414:7
1553527527773	Toolkit.Telemetry	WARN	TelemetryStorage::_scanArchive - have seen this id before: 820f0da1-7938-48f0-bf1b-5e442ebcbdc3, overwrite: false
1553527527773	Toolkit.Telemetry	WARN	TelemetryStorage::_scanArchive - have seen this id before: 0f55f57b-b347-4569-8033-f5b9ca577f41, overwrite: false
Flags: needinfo?(mdeboer)

Note that the ReferenceError: title is not defined ActiveSessionManager.js:414:7 is referring tabs aside extension file

I'll try to go few days with that extension disabled.

Status: NEW → UNCONFIRMED
Ever confirmed: false

Hi Honza, sorry for the late reply here! I was about to recommend trying the same thing as you suggested in comment 3. Please let me know how it goes. Meanwhile, I'll check out that extension to see how it might break the Session Restore process.

Flags: needinfo?(mdeboer)
Blocks: ss-reliability
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3

Thanks! I'm keeping the addon disabled now. To make sure it's interference with it may need few days to confirm.

If it does, then the followup would be to make sure some more that WebExtensions can't break Session Restore in any way.

Just reproduced with tabs aside disabled, exact steps:

  • have two new windows open (total of 5)
  • restart for daily update; this time it weirdly took a long time to close
  • got "restore session" window (might be a shutdown crash or some js code exception, but nothing found in about:crashes...)
  • clicked "restore"
  • result: the oldest window was lost + one of the new windows was lost (got total of 3 windows on restore)

I didn't check the browser console this time but I think this confirms the issue is inside our session restore code. I will do more retries to confirm. There are more addons still enabled, but I don't think any of them would be involved; I'll definitely try to isolate them too, but first let's try to dig in a bit more:

  • Is there some logging I could turn on for session store? I once touched that code and there was something.

  • Another thing to look after is probably the state of session store files in the profile, before and after shutdown and after another browser start to see when the breakage possibly happens (shutdown or start). I'm not sure how the file structure works, though.

    in the sessionstore-backups dir:

    • recovery.jsonlz4 is the current running session, periodically flushed, right?
    • what is previous.jsonlz4?
    • what is recovery.baklz4?
    • then there are upgrade.jsonlz4-<date>, what are those?

    sessionstore.jsonlz4 in the root profile dir is flushed on shutdown, right?

Mike, please see comment 7, I stated some questions there.

Today I got a single, blank window after restart; no new windows left open before that...

console:

1553775008692	addons.webextension.{3923146e-98cb-472b-9c13-f6849d34d6b8}	WARN	Loading extension '{3923146e-98cb-472b-9c13-f6849d34d6b8}': Reading manifest: Error processing key: An unexpected property was found in the WebExtension manifest.
1553775008720	addons.webextension.treestyletab@piro.sakura.ne.jp	WARN	Loading extension 'treestyletab@piro.sakura.ne.jp': Reading manifest: Error processing variable_color_icons: An unexpected property was found in the WebExtension manifest.
this.action is undefined browser-pageActions.js:1110
    updateEngines chrome://browser/content/browser-pageActions.js:1110
    updateOpenSearchBadge chrome://browser/content/browser.js:4179
    onLinkIconAvailable chrome://browser/content/browser.js:5596
    callListeners chrome://browser/content/tabbrowser.js:746
    _callProgressListeners chrome://browser/content/tabbrowser.js:765
    setIcon chrome://browser/content/tabbrowser.js:847
    onDOMContentLoaded chrome://browser/content/browser.js:1439
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMWindowUtils.removeSheetUsingURIString]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://gre/modules/ExtensionCommon.jsm :: runSafeSyncWithoutClone :: line 65"  data: no]
    runSafeSyncWithoutClone resource://gre/modules/ExtensionCommon.jsm:65
    cleanup resource://gre/modules/ExtensionContent.jsm:353
    close resource://gre/modules/ExtensionContent.jsm:814
    destroyed resource://gre/modules/ExtensionContent.jsm:889
    observe resource://gre/modules/ExtensionContent.jsm:905
Flags: needinfo?(mdeboer)

Hi!

I've the same problem since "Firefox Developer Edition 67 b1". I've five profiles on two different hosts each. Funny enough the problem only occurs with some profiles. Other profiles are not affected (at least not until now). All profiles basically use the same extensions. And most of the time if the old session is not correctly restored I got the first three tabs of the old session and that's it. ATM I basically have to restore some profiles daily from "sessionstore-backups" directory. Sometimes I can restore it from "previous.jsonlz4", sometimes I need to recover from one of the "upgrade.jsonlz4-..." files. Since my tabs don't change too much I'm happy to get at least most of my tabs back.

I've now installed SessionSync extension because I can't rely on Firefox builtin session handling any more. I'm using Developer Edition basically since version 58 and never had any big issues but this is a very annoying bug.

In general I haven't changed my extensions since Firefox 60 anymore. So I doubt that it's a bug caused by extension. The problem definitely started after I upgraded and used "Firefox Developer Edition 67 b1" the first time and it's still in beta 5 which I'm currently using.

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0
Version: 67.0b5
OS: Linux 5.0.4-arch1-1-ARCH # Archlinux

Please let me know when you need further information or if I can help to debug the problem. Here is the list of extensions I'm using if that is of interest:

Canvas Blocker
Cookie AutoDelete
Decentraleyes
Enhancer for YouTube
Firefox Multi-Account Containers
LoadTabOnSelect
Ope nTabs Next to Current
SessionSync
Switch Container
TabCenter Redux
Tampermonkey
uBlock Origin
uMatrix
Undo Close Tab
Vue.js devtools

Thanks, Robert, for the list of extensions. They don't intersect with any of mine, so it's probably really not an extension issue, but I would not rule that out that easily. Extensions automatically update and may suddenly contain bugs. Also, the problem could potentially be a more general interaction of an extension with a commonly used browser API we might broke recently.

If you can reproduce regularly, would you be willing to find the regression range or changeset with https://mozilla.github.io/mozregression/ ? It automatically bisects a version range and allows you to have a base profile (with which you can reproduce the problem) that is cloned for every test run, so it might be quite convenient. For me the failure happens intermittently only, so it's quite hard to do that.

Thanks!

Flags: needinfo?(firefox)

Hi Honza, I tried to install mozregession but that gives me only a error when I try to start it:

Traceback (most recent call last):
  File "/home/travis/build/mozilla/mozregression/venv/local/lib/python2.7/site-packages/cx_Freeze/initscripts/__startup__.py", line 14, in run
  File "/home/travis/build/mozilla/mozregression/venv/local/lib/python2.7/site-packages/cx_Freeze/initscripts/Console.py", line 26, in run
  File "mozregui/main.py", line 3, in <module>
  File "./mozregui/patch_requests.py", line 17, in patch
  File "/usr/local/lib/python2.7/dist-packages/requests/__init__.py", line 43, in <module>
  File "/usr/local/lib/python2.7/dist-packages/urllib3/__init__.py", line 8, in <module>
  File "/usr/local/lib/python2.7/dist-packages/urllib3/connectionpool.py", line 35, in <module>
  File "/usr/local/lib/python2.7/dist-packages/urllib3/request.py", line 3, in <module>
  File "/usr/local/lib/python2.7/dist-packages/urllib3/filepost.py", line 12, in <module>
LookupError: no codec search functions registered: can't find encoding

I tried to set PYTHONPATH accordingly but sadly no luck. But looks like I'm not the only one: https://bugzilla.mozilla.org/show_bug.cgi?id=1503358

Yesterday I installed beta6. Today the first profile I started (which I always start first) was missing most of the tabs again. Luckily with SessionStore extension I'm now at least able to recover all tabs without copying files somewhere in the profile directory. All other profiles came back with all tabs like I left them.

So at the moment the only thing I can definitely say is that the problem started with the upgrade to Firefox Developer Edition 67 beta1 from the latest Firefox Developer Edition 66 (beta14 was that last one released here AFAICS). Before I start to work I basically always check if there is a Firefox update available via Archlinux package manager pacman. And if so I install it. And after I did the upgrade to Firefox Developer Edition 67 beta1 and started my first profile as usual most tabs where gone. AFAIR the same was true for another profile but three out of five profiles I use hadn't this issue and this three profiles never had any issues during all the upgrades from Firefox Developer Edition 67 beta1 up to beta6 now.

Maybe I should delete the two profiles in question and create new ones. Maybe that solves the problem. Maybe it's a problem just with older profiles? But I can't remember when I created them.

I compared the addons of two of the working profiles again with my "main" profile (that's the one I always start first) that has the issue. One of working profiles had additionally "FoxyTab" extension installed (in comparison to my "main" profile) and the other working profile had "Tab Session Manager" installed (which I didn't used so far so I removed it now). My "main" profile has "Tampermonkey" and "Vue.js devtools" extension installed which the other (working) both don't have. While I really doubt that any of the two extensions causing the issue (as they don't have anything to do with session handling) I've now three profiles in pair regarding the installed extensions (two that worked fine until now and one which had the session restore issue). We'll see if that makes a difference.

I know the provided information won't help that much but that's the only thing I can report ATM.

Flags: needinfo?(firefox)

(In reply to Honza Bambas (:mayhemer) from comment #7)

Just reproduced with tabs aside disabled, exact steps:

  • have two new windows open (total of 5)
  • restart for daily update; this time it weirdly took a long time to close
  • got "restore session" window (might be a shutdown crash or some js code exception, but nothing found in about:crashes...)
  • clicked "restore"
  • result: the oldest window was lost + one of the new windows was lost (got total of 3 windows on restore)

I didn't check the browser console this time but I think this confirms the issue is inside our session restore code.

That's always hard to tell. Most often it's in some other (sometimes) bizarre area, so we can only be sure after careful analysis.

I will do more retries to confirm. There are more addons still enabled, but I don't think any of them would be involved; I'll definitely try to isolate them too, but first let's try to dig in a bit more:

Thanks much, I really appreciate it! This is often something isolated to a specific profile/ setting, so anything you can find that may be helpful is very much appreciated. In about:support you can copy & paste your current settings and installed addons. There shouldn't be anything privacy sensitive in there, but it's good to prune it before you post ;-)

  • Is there some logging I could turn on for session store? I once touched that code and there was something.

Yes, there's browser.sessionstore.debug, which you can flip to TRUE.

  • Another thing to look after is probably the state of session store files in the profile, before and after shutdown and after another browser start to see when the breakage possibly happens (shutdown or start). I'm not sure how the file structure works, though.

    in the sessionstore-backups dir:

    • recovery.jsonlz4 is the current running session, periodically flushed, right?
    • what is previous.jsonlz4?
    • what is recovery.baklz4?
    • then there are upgrade.jsonlz4-<date>, what are those?

    sessionstore.jsonlz4 in the root profile dir is flushed on shutdown, right?

You can read all about it here in David's excellent post from 2014: https://dutherenverseauborddelatable.wordpress.com/2014/06/26/firefox-the-browser-that-has-your-backup/

sessionstore.jsonlz4 is indeed flushed to disk during normal/ clean browser shutdown (which should include an upgrade) and periodically during browser runtime. The upgrade-* files contain the last known working state from before a browser upgrade.

Random observation: it looks like that at some point the windows are not recorded in sessionstore.jsonlz4, which means that three things could be wrong:

  1. Upon upgrade shutdown, the browser windows are closing too soon, so their info can not be collected anymore by sessionstore.
  2. Sessionstore stopped flushing to sessionstore.jsonlz4 at some point and the upgrade shutdown resulted in a crash, meaning that the flush-on-shutdown didn't get a chance to complete.
  3. Whilst collecting window data, an error was thrown for the missing windows, which may have resulted in them being skipped and not recorded in sessionstore.jsonlz4.

As you can see, this is really machine & profile specific. It'd be very helpful if you could get logging output during an upgrade shutdown. At some point I could potentially also take a look at your profile, but that's really privacy sensitive and only a last-resort.

Flags: needinfo?(mdeboer)
Priority: P3 → P1

This seems to happen at shutdown. I have saved the sessionstore-backups dir before and after shutdown. recovery.jsonlz4 is way bigger before shutdown (~4MB) than after shutdown (~700kb). I was closing the browser with File/Exit having the consoled open and no errors were seen during the short blip before all windows were closed; hard to say if errors would make it to the console in time.

Today I can see some weird errors like this in the console during normal run:
Error: TelemetryStopwatch: key "FX_SESSION_RESTORE_COLLECT_DATA_MS" was already initialized SessionSaver.jsm:53:33
Error: TelemetryStopwatch: key "FX_SESSION_RESTORE_COLLECT_ALL_WINDOWS_DATA_MS" was already initialized SessionStore.jsm:3415:24

Flags: needinfo?(mdeboer)

I did not forget about this bug, I'm just so busy that I rather let my firefox and dev machine running all the time, that to fight this bug...

Anyway,

  • with the log pref on, I can see following errors regularly appearing, in one flash:
  1. Error: TelemetryStopwatch: key "FX_SESSION_RESTORE_COLLECT_DATA_MS" was already initialized SessionSaver.jsm:53:33
  2. Error: TelemetryStopwatch: key "FX_SESSION_RESTORE_COLLECT_ALL_WINDOWS_DATA_MS" was already initialized SessionStore.jsm:3415:24
  3. TypeError: data is nullPrivacyFilter.jsm:49:9

I'm on https://hg.mozilla.org/mozilla-central/rev/16d953cca41483b114d70a3132fbcfe60755708f, hence:

  1. https://hg.mozilla.org/mozilla-central/file/16d953cca41483b114d70a3132fbcfe60755708f/browser/components/sessionstore/SessionSaver.jsm#l53
  2. https://hg.mozilla.org/mozilla-central/file/16d953cca41483b114d70a3132fbcfe60755708f/browser/components/sessionstore/SessionStore.jsm#l3415
  3. https://hg.mozilla.org/mozilla-central/file/16d953cca41483b114d70a3132fbcfe60755708f/toolkit/modules/sessionstore/PrivacyFilter.jsm#l49

no stack :(

these appear on and on during typing of this comment, for instance. I know we store text-areas in forms in the session, so these exceptions could be the cause of this whole bug.

  • the sessionstore-backups\recovery.jsonlz4 file has not been modified on disk for more than a week (cca the time my FX is up)
  • actually, none of the session store files seems to be flushed

I'm scared (sure actually) that with closing FX I will loose my session again....

The errors I observed in the browser console disappeared recently. It's still worth to look into the code and try to figure out what could cause that (or what could fix that).

I think this could have something to do with enabling studies (as I recently enabled them for the add-on issue fix).

Just happened to me today again (as stated in the title) but I didn't check the browser console before closing firefox :/

FYI: I rather just wiped out my session (deleted all session-* stuff from my profile) and started over then to deal with this super annoying bug.

Flags: needinfo?(mdeboer)

I guess I will do the same. It seems that the frequency got lower with Firefox Developer Edition 68 but it still happens from time to time. Without the SessionSync extension I would be totally lost. But since this happens only to the older profiles that I have my assumption would be that this maybe only happens to profiles that existed before the big FF 57 Quantum update. AFAIR I created the other profiles later. But that's only digging in the dark. It's just strange that this problem doesn't happens to more people. Since nobody else commented so far I guess for most people the FF 66 -> 67 update worked just fine.

I've been seeing this on and off in Nightly since April or March -- I think about 3-5 times. But I almost never close my browser these days, because I'm afraid of this bug.

My profile might be old -- I have a key3.db from Jan 2018.

Possibly fixed by bug 1553413?

Something indeed seems to have changed. The problem didn't happened anymore since around Firefox 68 b5 or so. And I restarted one of the older profiles quite often today while playing around with KDE GTK appearance settings. So yeah, maybe we can be happy again now ;-)

Hello! I have tried to reproduce the issue using fx 93.0a1(08-31-2021) but unfortunately I was unable to reproduce it. I will change the severity to a lower one. If the issue is still a high priority please feel free to change the severity to an appropriate state.

Thank you and have a nice day!

Severity: major → S4

(In reply to Robert from comment #21)

Something indeed seems to have changed. The problem didn't happened anymore since around Firefox 68 b5 or so. And I restarted one of the older profiles quite often today while playing around with KDE GTK appearance settings. So yeah, maybe we can be happy again now ;-)

Honza, do you agree?

Flags: needinfo?(honzab.moz)

Redirect a needinfo that is pending on an inactive user to the triage owner.
:dao, since the bug has high priority, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(honzab.moz) → needinfo?(dao+bmo)
Severity: S4 → S3
Priority: P1 → P3
Flags: needinfo?(dao+bmo)
You need to log in before you can comment on or make changes to this bug.