Resolved [Fix in review] 2021.2.0a13 - Never ending "Importing Assets/AssetDatabase.ParallelEnumeration"

Hi,

Everything is in the title. This "importation" never ends until I kill Unity in the task manager since there is no way to close it. "Cancel Batch" button is greyed out. I'm talking about a completely empty project here.

The damn dialogue reappears on reopening the project.

 

Hi,

Thank you for taking care!

1. Linux Mint, the details are in my profile (link in my signature),
2. ext4,
3. being a brand new project, there was no symlink inside it unless the project creation process creates some?
4. I have deinstalled 2021.2.0a13 and deleted the project. I suspect that it was never fully created anyway because of that weird thing happening.

I hope you'll find an explanation, I'm curious.

 

Thanks!

Oh, I forgot! the project created was a 2D project. Sorry about that.

 

This happened on project creation.

 

I don't understand, you didn't create it from Unity Hub after selecting 0a13?

Give me some time, I'm going to reinstall 0a13 and create a 2D project with it.

 

It happened again. After installing 0a13, I created a 2D project and the window was there.

​

I managed to stop it by deleting the temp folder (Unity was still running).

I tried to close Unity but having deleted the temp folder, a file was missing and I got a message asking if I wanted to force quit Unity. I forced quit.

Then I reopened the project. Apparently everything was working but the damned window popped up again after I quit the Package Manager that I had open to check what packages were installed.

Right now, ten minutes after, it's still there... and this time, deleting the temp folder is of no help. I need to kill Unity in the task manager.

How do I send you the project (80 mB in a zip)?

 

Thank you for filing a bug report!

https://issuetracker.unity3d.com/is...-inside-assetdatabase-dot-parallelenumeration

The fix mentioned is working; I hope I'll be credited for helping with the Alpha, although the bug was not reported by me! @LeonhardP

 

I don't think it's Linux-specific - this has happened to me during editor startup on Windows 10.. at least I'm pretty sure that's the message that was showing while it was stalled. If it happens again I'll confirm.. iirc happened once in 0a13 and once in 0a14. I had to close the editor from Task Manager, but opening the editor again after that and everything works fine.