#Where does "JobTempMemoryLeakValidation" log to?
1 messages · Page 1 of 1 (latest)
Preferences -> Jobs -> Leak Detection Level
Turn on stack traces
not there are currently a bunch from the packages that will show up (hopefully cleaned up next release)
Yeah, I mean where do I see said stack trace?
it will appear in your log
however it will require a domain reload though before it will appear
something like this
Hmm, I am not seeing that at all :/
I am on unity 2022.2.20
should be fine
A short (some what janky) video showing what I am doing.
I have restarted Unity a number of times already
that setting wont really help you
What setting do I want then?
^
(that said i suspect this leak isn't even your leak)
That doesn't do anything either
Yeah I did that. Still nothing
I am very confident that it is. That I do know.
I am using a lot of NativeArrays
To clarify, I am not using Entities. I am just using Jobs
And just incase I am doing something wrong that I am missing. This is what I am doing. The job runs on Start
are you completing the job?
Yup
It isn't like I couldn't read through the code and stuff to figure out what it is I am not disposing of. But for now and the future it would be easier if I could just see the stack trace of it instead
this is why i think you're either using untracked memory or it's not your leak
because it's very clear when code you write leaks if you turn on stacks
Huh interesting. Right so that does produce a stacktrace
Ahh @tawdry orbit so it seems that NativeLists are not tracked
oh
what version of collections are you using?
because list works fine
but you need the latest collections package
2.1.0-pre.18
yeah update, latest is 2.1.4
2.1.1 is when collections added tracking
Fixed
Properly tracks allocations made from the collections package such that when Unity.Collections.NativeLeakDetectionMode is NativeLeakDetectionMode.Enabled or NativeLeakDetectionMode.EnabledWithStackTrace, native memory leaks will be reported upon domain reload.
Of course it was haha
I think I need to upgrade to 2022.3 since I am not seeing 2.1.4 in the package manger