Closed
Bug 262097
Opened 20 years ago
Closed 19 years ago
keep getting "nativeMethod.call is not a function"
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bugzilla, Unassigned)
Details
My console is almost always flooded with:
Error: nativeMethod.call is not a function
Source File: chrome://global/content/XPCNativeWrapper.js
Line: 94
using latest nightly build on winxp.
been getting these errors for months now
Comment 1•20 years ago
|
||
> using latest nightly build on winxp.
Latest nightly build of what?
I don't see this in a SeaMonkey Linux trunk build...
Reporter | ||
Comment 2•20 years ago
|
||
Mozilla 1.x
i normally get this after running Mozilla for a while
Comment 3•20 years ago
|
||
With: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041105
MultiZilla/1.6.4.0b
and previous builds (i try to follow the nightly builds when I can) I've been
seeing the same error message quite frequently. Not sure what this is or what
it breaks. I almost always see it when checking for other errors.
The JavaScript console points to line 92 of XPCNativeWrapper.js:
_doImportProperty:
function(aPropName)
{
var nativeMethod = Components.lookupMethod(this.mUntrustedObject,
aPropName);
var theGetter = function()
{
return nativeMethod.call(this.mUntrustedObject); <<-- line 94
};
var theSetter = function(val)
{
return nativeMethod.call(this.mUntrustedObject, val);
};
this.__defineGetter__(aPropName, theGetter);
this.__defineSetter__(aPropName, theSetter);
}
};
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 4•19 years ago
|
||
This was moved to native code, the error should be gone.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 5•19 years ago
|
||
No specific bug / patch referenced as the fix.
-> WORKSFORME
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•19 years ago
|
Status: REOPENED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WORKSFORME
Comment 6•19 years ago
|
||
The relevant bug is bug 281988. So this really should have stayed RESOLVED FIXED.
Comment 7•19 years ago
|
||
That's all that was needed. :)
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Updated•19 years ago
|
Status: REOPENED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•