Native collection has not been disposed, even if I call dispose properly
So this is my code And I only ever call it in order of schedule and then complete, but I still get tons of errors saying a native collection has not been disposed? The only unusual thing is that "points" on the outside of the job is a static array because two instances of the classes share the same point set to assure they get cut out the same, but I just tried it with a non-static version of points and it didn't get rid of any errors.
This is really annoying, and I've tried persistent allocator and saying the new job is dependent on the last, but that didn't provide good results, it just broke the math and make it stop working as expected. Enabling "full stack trace" literally didn't change any of the error messages or provide any help, even after restarting the editor, so seems like unity is trying to make me give up on multithreading given there's a million different documentations on this, none of which answer my questions because every other problem was people just not calling "dispose" but I'm actually calling dispose, so I'm clearly not messing up that.
Any help is appreciated.
Your answer
![](https://koobas.hobune.stream/wayback/20220613012645im_/https://answers.unity.com/themes/thub/images/avi.jpg)
Follow this Question
Related Questions
Frame Debugger doesn't let me input script to objects or insert objects. 0 Answers
Why isn't my mobile single joystick showing on screen, PLEASE HELP? 1 Answer
Using multiple cameras for different render distances causes weird shadow effect? 0 Answers
[HELP] Audio does not play in inspector, game mode, or in build. Unity 5.6.2 0 Answers