Search Issue Tracker
Fixed
Fixed in 1.8.13, 2.0.0-pre.5
Votes
7
Found in [Package]
1.8.7
1.8.10
Issue ID
BUR-2559
Regression
Yes
"Burst internal compiler error: Burst.Compiler.IL.CompilerException: Error while verifying module" error is thrown when debug information is being generated
Reproduction steps:
1. Open the “StreamlinedProject.zip“ project
2. Observe the Console window
Expected result: No compilation errors
Actual result: Error is thrown “Burst internal compiler error: Burst.Compiler.IL.CompilerException: Error while verifying module: DISubprogram attached to more than one function”
Reproducible with: 1.8.7 (2021.3.32f1, 2022.3.7f1, 2023.1.10f1, 2023.2.0b5), 1.8.10 (2021.3.32f1, 2022.3.13f1, 2023.1.20f1, 2023.2.0b18, 2023.3.0a13)
Not reproducible with: 1.8.4 (2021.3.32f1, 2022.3.2f1, 2023.1.1f1, 2023.2.0a20)
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: Intel macOS 14
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
gilley033
Jan 08, 2024 23:51
@Marc_Ducret
No, I gave up on it. In my case the offending code is not in a pre-compiled assembly, however my setup is a little weird.
Basically, I have a base abstract class that inherits from ScriptableObject that IS within a precompiled assembly. There are two implementations of this, one in the assembly as well that does not use Burst, and one outside that is basically the same code but with the BurstCompile attribute. However, I have tried changing the names of the structs (before they had the same name across both implementations), but that doesn't fix the issue.
So this may be related to using a pre-compiled assembly, but I'm still not sure how.
Marc-Ducret
Dec 04, 2023 22:52
For your information, in my case, the problem was compiling with Burst code in a precompiled assembly.
Marc-Ducret
Dec 04, 2023 17:14
Also running into this, did you find a workaround or identify the root cause?