Closed Bug 1514119 Opened 7 years ago Closed 7 years ago

Building firefox w/ --disable-launcher-process causes 'Couldn't load XPCOM' failure.

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Version:
65 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox64 --- affected

People

(Reporter: jsearle3, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/18.17763 Steps to reproduce: Build firefox with the following in a mozconfig file: ac_add_options --disable-launcher-process and then run firefox.exe Actual results: Fiewfox fails @ line 226 in nsBrowserApp.cpp because XPCOMGlueLoad() can't open the file dependentlibs.list as it doesn't exist. Expected results: I'm not sure what just changed. I've been building firefox with this option for a month or so because it greatly simplifies setting breakpoints in Visual Studio 17 on Windows.
Took in the latest update and built firefox, and then ran it. works now. Stepped through code to see why it now works. It seems the dependentlibs.list is being generated now by the build.
Based on Comment 1 from the reporter, changing status to RESOLVED WORKS FOR ME. If anyone can still reproduce it, feel free to reopen the issue and provide more information.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
status-firefox64: --- → affected
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.