Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Memory leak with _global_sinks
See original GitHub issuein core.py the set _global_sinks captures all constructed sink objects. What was it used for?
This should be either removed or replaced with a WeakSet
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (13 by maintainers)
Top Results From Across the Web
Memory leak in C++ and How to avoid it? - GeeksforGeeks
Memory leakage occurs in C++ when programmers allocates memory by using new keyword and forgets to deallocate the memory by using delete() ...
Read more >Understanding Memory Leaks in Java - Baeldung
A Memory Leak is a situation where there are objects present in the heap that are no longer used, but the garbage collector...
Read more >Memory leak? on Sample code | Apple Developer Forums
I am currently developing applicsation using Metal for MacOS. When the sample program "CreatingAndSamplingTextures" is run, the memory used will gradually ...
Read more >How to Detect Memory Leaks in Java: Causes, Types, & Tools
A memory leak is a situation where unused objects occupy unnecessary space in memory. Unused objects are typically removed by the Java ...
Read more >Memory Leaking Scenarios - Go 101
When programming in a language supporting auto garbage collection, generally we don't need care about memory leaking problems, for the runtime will collect ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for the clarification, @CJ-Wright , I probably should have known that. I wonder, then, if streamz should provide an explicit API for working with this global reference store, or should there be something cleverer, whereby a sink removes itself upon the destruction or removal of its upstream (perhaps in conjunction with #248 ).
Specifically, we store downstreams as weakref, but concrete upstream, otherwise all instances would insta-disappear in every case. The assumption for ordinary nodes is that either a downstream node will refer to them, or the user will capture a reference themselves.