Closed Bug 649873 Opened 13 years ago Closed 13 years ago

App Tabs lost after forced system reboot

Categories

(Firefox :: Session Restore, defect)

4.0 Branch
x86
Windows 7
defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bogdan2150, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0

After a power outage I restored the last session and lost all the app tabs. The app tabs were visible before I selected the restore option.

Reproducible: Didn't try
Component: Tabbed Browser → Session Restore
QA Contact: tabbed.browser → session.restore
Version: unspecified → 4.0 Branch
You should be able to restore lost sessions from the history menu. If you have not restarted Firefox the session should be there.
Works for Me on:
Build ID: Mozilla/5.0 (Windows NT 6.1; rv:5.0a2) Gecko/20110413 Firefox/5.0a2

I unplugged the PC power cord while running Firefox which would be the equivalent of a power outage. On restart, Firefox restored all the tabs (including the app tabs) from the previous instance (before the outage).

Marking this as WorksForMe. If you consider otherwise, feel free to reopen the bug. Thanks
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
I tried to reproduce the incident again and didn't happened. Thanks for checking this out.
When Firefox is freezed (i.e. because some app used all resources and freezed whole system and Ff) i pressed reset button, Firefox lost app tabs

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0a2) Gecko/20110806 Firefox/7.0a2


Reproducible : Sometimes
Maybe they should be saved like Home Page is saved? (then they always will be loaded independent from any troubles)

Maybe even more - they should behave like they are now, but they should be visible near HomePage (in Options menu) and should be possible to modify from that menu too?

this should resolve any problems with app tabs for sure
You need to log in before you can comment on or make changes to this bug.