#24 Proxied procs aren't getting cleaned up - Johnson

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#24 ✓resolved

Proxied procs aren't getting cleaned up

Reported by John Barnette | April 2nd, 2008 @ 02:01 AM

The JSClass for JSObjects representing JSFunctions (js_FunctionClass) just uses JS_FinalizeStub, which means we aren't cleaning Ruby procs out of @gcthings or context->rbids. Consider setting the stub for all JSFunctions if we can safely get away with it.

Comments and changes to this ticket

John Barnette April 2nd, 2008 @ 10:54 AM
- State changed from “new” to “open”
- Title changed from “Proxies procs aren't getting cleaned up” to “Proxied procs aren't getting cleaned up”
John Barnette April 3rd, 2008 @ 10:14 AM
Yeah, we should just reach in to js_FunctionClass and inject a custom finalize stub. See if it has the magical "this is a Ruby proc" marker property, and, if it does, cleanup as normal.
John Barnette April 7th, 2008 @ 03:55 PM
Alternatively, we could start having a lot more JSland proxy classes:
- JSProxyClass, for most Ruby objects, including Hashes
- JSArrayProxyClass, for Ruby arrays
- JSProcProxyClass, for Ruby procs
John Barnette April 20th, 2008 @ 10:49 PM
- State changed from “open” to “resolved”

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.