Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GM_apiLeakCheck issue when stack.filename is "self-hosted" #69

Closed
supahgreg opened this issue Dec 1, 2012 · 2 comments
Closed

GM_apiLeakCheck issue when stack.filename is "self-hosted" #69

supahgreg opened this issue Dec 1, 2012 · 2 comments
Labels
Milestone

Comments

@supahgreg
Copy link
Contributor

When calling an API function from within a self-hosted JS builtin (e.g. Array#forEach), at a certain point the stack.filename will be "self-hosted" (when stack.name === "forEach"). This value causes GM_apiLeakCheck to throw an access violation error, since it doesn't begin with "chrome".

// ==UserScript==
// @id             bug462300test@phob.net
// @name           Mozilla bug 462300 test
// @include        http://phob.net/*
// @run-at         document-end
// ==/UserScript==

// Does not work.
["bar"].forEach(function(aThing) {
  GM_setValue("foo", aThing);
});

Currently @ Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20121201 Firefox/20.0

Info:
https://bugzilla.mozilla.org/show_bug.cgi?id=462300
http://hg.mozilla.org/mozilla-central/annotate/ecdf0e332f17/js/src/jscntxt.cpp#l383
https://developer.mozilla.org/docs/SpiderMonkey/Internals/self-hosting

@nmaier
Copy link
Member

nmaier commented Jun 1, 2013

@erikvold
Copy link
Member

I'm going to archive the repo soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants