To add to what I wrote above - currently we have 2 open jira bug reports which represent 2 different ImportWorker crashes:
- for one we have a fix already and now in the process of landing and backporting it;
- for the second one (which @AstoraGray reported above) - Materials/URP team is investigating it, but there is no fix yet.
Unfortunately both those bug reports are internal, which means that they do not have a public IssueTracker link for tracking..
As additional note - we are working on improving the error log, so hopefully we will be able to transfer crash CallStack from AssetImportWorker file into Editor Console - so instead of
Unexpected transport error from import worker 3
you will in addition see the Call Stack immediately in the Console.
But this change is also still in works