Search Issue Tracker

Fixed in 2018.3

Fixed in 2018.2

Votes

22

Found in

2018.2.0b8

Issue ID

1051393

Regression

No

[Il2CPP][.Net 4.x] Crash in "il2cpp::utils::Debugger::InitializeTypeSourceFileMap()" at startup

IL2CPP

-

Reproduction steps:
1. Open the project from the attached 'drive.google.com' link.
2. Go to "File > Build Settings" and remove an empty scene from the "Scenes In Build" list.
3. Select the 'BuildPipeline' asset in the Project view.
4. Set Build to iOS and click Build.
5. Open and build the Xcode project in the project folder > Target > iosbuild.

Actual behavior:
- Crash
- Full call stack attached in the Edit below.

--
* frame #0: 0x0000000101cc6e20 `il2cpp::utils::Debugger::InitializeTypeSourceFileMap() at Debugger.cpp:120 [opt]
frame #1: 0x0000000101cc7188 `il2cpp::utils::Debugger::Start() at Debugger.cpp:146 [opt]
frame #2: 0x0000000101cbfb5c `il2cpp::vm::Runtime::Init(char const*, char const*) + 2576
frame #3: 0x0000000101478e30 `::InitializeIl2CppFromMain() at MonoManager_Il2Cpp.cpp:257 [opt]
frame #4: 0x0000000100e641e8 `::UnityInitApplicationNoGraphics() at LibEntryPoint.mm:177 [opt]
frame #5: 0x00000001000f7b60 `::-[UnityAppController application:didFinishLaunchingWithOptions:](self=0x0000000106d73d20, _cmd=<unavailable>, application=<unavailable>, launchOptions=<unavailable>) at UnityAppController.mm:263 [opt]
--

Reproduced with:
2018.2.0b10

Not reproducible with:
2017.4.6f1, 2018.1.7f1

Note:
- Possibly a regression, but it may be a project compatibility issue with older Unity versions using custom builder.

Comments (13)

  1. 91309587c8db6442fa44f393d52348fe?d=mm

    Thoptv

    Jun 21, 2019 08:40

  2. 31ac5763bd2ea2af81f7ea3542a85d32?d=mm

    jpmorgan_bfg

    Sep 14, 2018 18:30

    Just reproduced this while building with 2018.2.7f1

  3. 84f74042d367a687f175487fe6a5c9b5?d=mm

    Josepht45

    Sep 10, 2018 16:08

    Issue still here in version 2018.2.7f1

  4. 42cbc8a97c7d4ec1ed807554d04cefbf?d=mm

    alonso_actionreaction

    Sep 03, 2018 18:20

    Still having this issue in 2018.2.6f1

  5. 84f74042d367a687f175487fe6a5c9b5?d=mm

    Josepht45

    Sep 03, 2018 12:56

    2018.2.6 has the same issue.

  6. 4d831347431d4b1bce560b95f071f073?d=mm

    BIMG

    Aug 28, 2018 09:44

    The same issue in 2018.2.5f1

  7. 0803e99e49446fbdde258d65ae03740b?d=mm

    QualityJohn_TT

    Aug 21, 2018 08:34

    I've been able to work around the issue by turniong off the BuildOptions.AllowDebugging flag in our debug build config

  8. 0803e99e49446fbdde258d65ae03740b?d=mm

    QualityJohn_TT

    Aug 20, 2018 14:07

    I'm seeing the same on Unity versions 2018.2.2f1 2018.2.3f1 and Unity 2018.2.4f1

    Does not affect builds in Release configuration

  9. C34bc8fbe55e88cecc47db697e16d8d9?d=mm

    inelisoni_unity

    Aug 16, 2018 11:06

    We have the same issue.
    Using Unity 2018.2.0f2

  10. B5973477b0d87cb1aa2aaf91d49b6b06?d=mm

    MapMan

    Aug 09, 2018 14:20

    Also should mention that I'm using .NET standard 2.0 backend.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.