harunadess

4y

Have to find a memory leak in a huge, legacy JS application that builds, renders and handles (most) of the basic logic for completing forms - that only works when compiled into a minified js and put in another application that builds into a phonegap based app.
Did I mention everything is bound to a G(lobal) namespace and the ViewModel/Controllers etc. all use JQuery and "this" references and .bind() everywhere?

Deadline of fix: end of today/early tomorrow.

rant

Ranter

Comments

2

p100sch

1375

4y

@iiii Have you heard of "the framework keeps references even if it shouldn't and you need to null them out by hand". Some C# frontend libs are very sensitive to event handlers and forgetting to unregister your handler on one component may cause the entire window to leak.

Fun I know but I have a memory profiler to help out.
1

apply-eval

19

4y

@p100sch The very same bullet that bit me, although I'm in Java. Keeping one tiny reference ends up keeping the entire chain of objects.
0

10Dev

2793

4y

@iiii not to my knowledge, but I’ve had projects where the previous developers have fucked with global variables so much that they happen anyway
1

perotti

777

4y

@Jortathlon put everything in a weakmap, see what sticks gg
1

magicMirror

10327

4y

... Shit.

Js engines for mobile keep multiple Memory roots. The roots are hard to detect, as those can be practically anything - for example, timers, or eventloops for UI interactions.

Try to take a memory heap dump, and analyse it.

devRant © 2021 Hexical Labs LLC
Privacy Policy | Terms of Service