You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
findjsobjects -r is useful for finding which objects reference a particular object. However, it doesn't find references through closures. We should either extend it to include closure references or else add a separate dcmd for that.
The text was updated successfully, but these errors were encountered:
On Fri, Feb 9, 2018 at 11:15 AM David Pacheco ***@***.***> wrote:
findjsobjects -r is useful for finding which objects reference a
particular object. However, it doesn't find references through closures. We
should either extend it to include closure references or else add a
separate dcmd for that.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#105>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABK2EAy_NF-8jpg4dWjEn8LONZf2C3jzks5tTJlqgaJpZM4SAZvV>
.
FWIW, a while ago I had quickly put together a change to help me do that while investigating a memory leak: misterdjules@79a93c4. It's not pretty and it's slow, but it definitely allowed me to root cause a problem I wouldn't have been able to root cause otherwise.
findjsobjects -r
is useful for finding which objects reference a particular object. However, it doesn't find references through closures. We should either extend it to include closure references or else add a separate dcmd for that.The text was updated successfully, but these errors were encountered: