How to interpret the output of -Ddebugmemory
#178
Unanswered
BigBoyBarney
asked this question in
Q&A
Replies: 1 comment
-
To add on to this, these blocks
probably comes from {% for prop in ["title", "episodes_total", "episodes_aired", "episodes_watched"] %}
widget.temp_signal_connections << data.notify_signal[{{prop.gsub(/_/, "-")}}].connect do
widget.overlay.{{prop.id}} = data.{{prop.id}}
end
{% end %} And then in the widget while signal = @temp_signal_connections.shift?
signal.disconnect
end So I assume the unnamed lines are all signals? I'm clearly disconnecting them though, how come the reference is still 1? Even doing something simple like signal = data.notify_signal["title"].connect do
widget.overlay.title = data.title
end
signal.disconnect results in Registering 7fac5a27a760 on ClosureDataManager, count: 0.
Deregistering 7fac5a27a760 from ClosureDataManager, count: 1.
Registering 7fac5a27a720 on ClosureDataManager, count: 0.
Deregistering 7fac5a27a720 from ClosureDataManager, count: 1.
Registering 7fac5a27a6c0 on ClosureDataManager, count: 0.
Deregistering 7fac5a27a6c0 from ClosureDataManager, count: 1. Is it supposed to be 1? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
Quick, probably silly question.
I ran into a traumatising memory leak / flood, even, so I thought I'd build the app with
-Ddebugmemory
to see what's up.I attached the output of an average test run.
output.txt
Something is very obviously leaking, but I don't know how to read the output to figure out what / why. Signals are killing me and I'm stumped 😭
Any tips, advice or pointers would be very much appreciated 🙏
Some of the lines have names, such as GridImageOverlay, but others don't, and are just like
What does this mean?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions