Closed Bug 961063 Opened 10 years ago Closed 10 years ago

firefox.exe still running (suspended) after right-clicking in apps list and selecting 'Close', opening new links doesn't work if other firefox process with -no-remote running

Categories

(Firefox for Metro Graveyard :: Shell, defect)

x86_64
Windows 8.1
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 382477

People

(Reporter: aryx, Unassigned)

References

Details

(Whiteboard: [testday-20140117])

Firefox Nightly 29.0a1 2014-01-16 on Windows 8.1 Pro 64 bit

After setting Nightly as default browser and switching to Metro mode, links opened from a different application are opened as expected in it. After closing Firefox by right-clicking its thumbnail in the application list and selecting Close, it's still running (in a suspended state).

Actual results:
1. Now links opened from a different application launch CommandExecuteHandler.exe, but neither Alt + Tab nor the application list show Firefox Nightly. In the process list, it's still in suspended state.
2. Tapping the Firefox Nightly icon from the taskbar creates only a rectangle like for a running application which lasts for just a few seconds.
3. Because firefox.exe is still running, launching a Firefox shortcut to a different binary doesn't work without -no-remote.
Component: Metro Operations → Shell
Product: Tracking → Firefox for Metro
Version: --- → Trunk
This issue happens if another Firefox instance is running (using -no-remote command line parameter), similar to bug 961081.
See Also: → 961081
Summary: firefox.exe still running (suspended) after right-clicking in apps list and selecting 'Close', opening new links doesn't work → firefox.exe still running (suspended) after right-clicking in apps list and selecting 'Close', opening new links doesn't work if other firefox process with -no-remote running
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.