Search Issue Tracker
Fixed in 2017.2.0f3
Votes
3
Found in
5.5.0p1
Issue ID
863484
Regression
No
'Frame not in module' when stepping into partial class if NodeCanvas is imported
How to reproduce:
1. Open attached project
2. Open 'test' script
3. Place breakpoint on line 8 (StartCoroutine(t1());)
4. Attach debugger
5. Step into t1
Expected behaviour: File in which partial class is defined is opened and debugging continues
Actual behaviour: 'Frame not in module' shown
Reproduced with: 5.4.4p1, 5.5.0p4, 5.6.0b3
Fixed in: Unity 2017.1 and newer thanks to new C# compiler.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is shown when launching a freshly created project
- Editor Windows dragging behavior is erratic/glitchy when a specific multi-display setup is used and the Editor window is not on the main display
- Meta Quest missing an icon in Build Profiles window in U6.0
- Foldout arrow indent is misaligned in the Inspector when used for Arrays or Lists
- Material import pipeline strips properties when it is added with a script
Add comment