Closed
Bug 797073
Opened 13 years ago
Closed 13 years ago
Metrofx gets spammed with an odd set of launch params
Categories
(Firefox for Metro Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jimm, Unassigned)
Details
Guessing this is the installer since it started recently. Might be in the ceh as well.
On startup we get a set of launch parameters that are a broken up path:
MetroAppShell::Run
XPCOM startup initialization complete
mozilla::widget::winrt::FrameworkView::SetWidget
MetroWidget::FindMetroWindow
mozilla::widget::winrt::FrameworkView::SetupContracts
Activation argument kind: Launch
Launch arg[0]: 'C:\Program'
Launch arg[1]: 'Files'
Launch arg[2]: '(x86)\Nightly\firefox.exe'
[JavaScript Error: "[Exception... "Component returned failure code: 0x804b000a (NS_ERROR_MALFORMED_URI) [nsICommandLine.resolveURI]" nsresult: "0x804b000a (NS_ERROR_MALFORMED_URI)" location: "JS frame :: jar:file:///C:/Program%20Files%20(x86)/Nightly/metro/omni.ja!/components/BrowserCLH.js :: resolveURIInternal :: line 25" data: no]" {file: "jar:file:///C:/Program%20Files%20(x86)/Nightly/metro/omni.ja!/components/BrowserCLH.js" line: 25}]
MetroWidget::Create
| Reporter | ||
Comment 1•13 years ago
|
||
The odd thing here is that we don't launch firefox.exe, Windows does. So maybe windows is picking something up it shouldn't from the reg.
| Reporter | ||
Updated•13 years ago
|
Component: Installer → General
Product: Firefox → Firefox for Metro
Comment 2•13 years ago
|
||
Jim are you still seeing this? I haven't seen this when i was working on similar code recently.
| Reporter | ||
Comment 3•13 years ago
|
||
I don't see this anymore.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
| Assignee | ||
Updated•11 years ago
|
OS: Windows 8 Metro → Windows 8.1
You need to log in
before you can comment on or make changes to this bug.
Description
•