Closed Bug 313268 Opened 20 years ago Closed 20 years ago

ChatZilla does not start after patch for bug 279839

Categories

(Other Applications Graveyard :: ChatZilla, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: fredbezies, Assigned: rginda)

References

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20051021 SeaMonkey/1.1a Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20051021 SeaMonkey/1.1a Simple. Just download last SM trunk build. Try to launch Cz... Reproducible: Always Steps to Reproduce: See details Actual Results: Cz crashes on start. Expected Results: Cz starts. Error message : "[Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]" nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame :: chrome://chatzilla/content/lib/js/utils.js :: getService :: line 568" data: no] + QueryInterface (function) 3 lines + message (string) 'Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]' + result (number) 2153185302 + name (string) 'NS_ERROR_XPC_GS_RETURNED_FAILURE' + filename (string) 'chrome://chatzilla/content/lib/js/utils.js' + lineNumber (number) 568 + columnNumber (number) 0 + location (object) + inner (object) null + data (object) null + initialize (function) 3 lines *"
Blocks: 279839
Do we know if this is limited to Mac? I'm still waiting for my Windows build.
Summary: Cz do not start after patch for bug 279839 → ChatZilla does not start after patch for bug 279839
No problems on my windows build. checkout finish: Fri Oct 21 18:26:20 2005 CET about:buildconfig Build platform target i686-pc-cygwin Build tools Compiler Version Compiler flags $(CYGWIN_WRAPPER) cl 13.10.3077 -TC -nologo -W3 -Gy -Fd$(PDBFILE) $(CYGWIN_WRAPPER) cl 13.10.3077 -TP -nologo -W3 -Gy -Fd$(PDBFILE) Configure arguments --enable-application=suite --enable-extensions=default,inspector --enable-optimize --disable-debug --disable-tests
Indeed, this also WFM on my Windows build of 2005102117: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9a1) Gecko/20051021 SeaMonkey/1.1a Chatzilla 0.9.67+ [SeaMonkey 1.1a/2005101602] (interesting that the two full IDs are different - probably bugs in the build system - I'm trusting the one in the title bar, 2005102117, not the nsIXULAppInfo one which ChatZilla has picked up, since I built it today not 5 days ago!)
Stinks like a mid checking bug, as official nightly (2005102109) is working perfectly :( Building a new SM with source up to date at 10:00 pm - 21st october, mozilla.org time. /me thinks this bug will be closed as INVALID soon...
It was a mid-checking bug :( Closing this bug as invalid...
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
I'm still seeing this with trunk build 2005102205 and current CVS. Launching chatzilla a second time (without closing SeaMonkey) works.
Status: RESOLVED → REOPENED
OS: MacOS X → All
Hardware: Macintosh → All
Resolution: INVALID → ---
Version: unspecified → Trunk
I'm not seeing this problem on a trunk seamonkey build on Windows. I created a brand new profile, started seamonkey, and was able to launch Chatzilla fine. Same with the latest nightly build (2005102208). JS component fastload should have little effect on SeaMonkey since the profile directory is unavailable when the JS components are loaded (that is, no XPC.mfasl is written). Can anyone provide an exact set of steps to see this problem, starting with a clean profile?
I see this bug with a pristine profile on linux. I can make the bug go away temporarily by deleting XUL.mfasl /and/ compreg.dat (deleting one or the other doesn't help). The next time I start up, I get this bug again.
BeOS, 2005-10-22-05-trunk: [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]" nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame :: chrome://chatzilla/content/lib/js/utils.js :: getService :: line 568" data: no] + QueryInterface (function) 3 lines + message (string) 'Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]' + result (number) 2153185302 + name (string) 'NS_ERROR_XPC_GS_RETURNED_FAILURE' + filename (string) 'chrome://chatzilla/content/lib/js/utils.js' + lineNumber (number) 568 + columnNumber (number) 0 + location (object) + inner (object) null + data (object) null + initialize (function) 3 lines
Looks like bug 279839 is also guilty for bug 313262, because like said in comment #8, deleting compreg.dat is a workaround for bug 313262 too.
Today's OS/2 trunk WFM, but I keep nglayout.debug.disable_xul_cache = true on this profile.
This should be fixed now from the checkin for bug 313612
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → FIXED
Product: Other Applications → Other Applications Graveyard
You need to log in before you can comment on or make changes to this bug.