Unity 2022.2 will crash when clicking the play button (reload domain) if the package “com.unity.jobs” is installed
2 Likes
Please clarify with any errors in console, and a bug report if you can make it would be REALLY valuable 
Even if its a trimmed down empty scene - it will include editor config / extra hardware or driver info Unity can use to help track the problem down.
It just crash and not enough time for us to look at anything in console
Check the log file.
That’s fine if you could go to the help menu → report a bug (without going into play mode) it should send the data why it crashes / recent logs to Unity.
edit: or post logs here as SpookyCat has mentioned.
This is my log
8284074–1085736–Editor.log.txt (45.1 KB)
My wild guess from looking at the crash stack trace: it crashes while pressing play because of “something” related to some “search operation” in the package manager window. As in, this has nothing to do with jobs, but rather some issue with the packages window UI.
Is the package manager window open? Does the crash go away if you close it?
In any case, reporting a bug would be best.
1 Like
No. Even just clean open the project and press play just like that it crash immediately
I also see that error is actually related to package manager. But there are no problem with any other package except jobs. Which if it’s me I would guess that jobs are trying to do something relate with its package dependency chain but it not support in 2022.2
This was listed as a known issue in the last alpha.
https://unity3d.com/unity/alpha/2022.2.0a18
Seem you are right. But the mention about it was missing from both 0a17 and 0b1 (yes, it crashed on 0a17 too)
I can’t even find issue with id UUM-7459 (this is reason why I hate report and issue system of unity)
Everytime domain was reloaded, this thing has been happening to me with 2022.2 alpha. b1 causing the same problem.
I thought this was apparent problem and should be fixed anytime soon. Maybe not eh?
Thanks. However
https://unity3d.com/search?refinement=issues&gq=UUM-7459
Or even
https://unity3d.com/search?refinement=issues&gq=MONO_CLASS_INFLATE_GENERIC_TYPE_WITH_MEMPOOL
Also
Yeah, the search is awful. I just construct the URL manually.
2 Likes
Okay b2, like b1, didn’t mention this as known issue and did not change anything. Still crashes.
I want to know what is to be listed as Known Issues and what is not. Why only a18 listed this as Known Issues? It’s not consistent I feel like.
I know we can see Issue Tracker at this point but it’s weird.
It there any way to avoid this issue? This is rather serious for me.
@nishikinohojo @prg-liulie Can you try updating to com.unity.collections-1.4.0? This package includes all the com.unity.jobs code and should resolve the issue which was due to circular references between com.unity.jobs and com.unity.collections exposed in 2022.
For existing com.unity.jobs users who do not use com.unity.collections, there is a new package com.unity.jobs-0.70.0-preview.7 which will pull in the dependency on collections automatically. Going forward com.unity.jobs has been superseded by com.unity.collections-1.4.0+. Let me know if you run into any issues.
Hope this helps!
3 Likes
So no official fixed as of yet?
@kevinmv
Thank you! It did fix the problem.
I am slightly surprised that you guys have decided to make them whole. But what must be done must be done I suppose.
Anyway I really am glad to see Unity officials care to answer some questions here.
1 Like
This is our official fix, so if there are any issue found please do let us know and we’ll take a look!
Happy to help! I’m glad it worked for you
2 Likes