How to reproduce:
1. Open the attached “EditorCrashBug” project
2. Drag and drop the attached "TestObj.obj" file to the Asset folder

Reproducible with: 2020.3.45f1, 2021.3.28f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a23
Not reproducible with: 2020.3.44f1

Reproduced on: macOS 13.3.1 (Intel) (by reporter), macOS 13.4.1 (Intel)

First few lines of the stack trace:
#0 0x007ff81b5d5a88 in strtol_l
#1 0x0000010ae5f834 in fbxsdk::FbxReaderObj::ParseVertexGroup(fbxsdk::FbxObjIndexGroup&, char*)
#2 0x0000010ae5cd2e in fbxsdk::FbxReaderObj::ParseObjFace(fbxsdk::FbxObjFace*, char*, int)
#3 0x0000010ae5ad1f in fbxsdk::FbxReaderObj::Read(fbxsdk::FbxDocument*)
#4 0x0000010ac87204 in fbxsdk::FbxImporter::ImportProcess(fbxsdk::FbxDocument*)
#5 0x00000105dbef7e in UnityFBX::DoImportScene(ImportScene&, ImportSettings const*, ImportMeshSettings*, bool)

Workaround: converting the file to .fbx format before importing will prevent the crash

-------------------------------------------

This bug was introduced during a recent update of the FBX SDK. The SDK is owned and built by Autodesk and they decide when to release a new version.

We found a fix and sent it to them but we don't know when they'll make it available.

We will publish this as soon as we get it but this is sadly out of our control.

Thank you and really sorry about the inconvenience