- New project.
- Add any node.
- Select node.
- New scene.
- CTRL+Up
- File->New
- Save changes = No
Heap corruption 2.5
Heap corruption 2.5
Consistently crash 2.5 with a heap corruption exception in ntdll.dll. Steps:
Re: Heap corruption 2.5
I can't seem to reproduce that here.
When you select a module and then press Ctrl+Up, it tries to replace the module with the previous one in the menu. Could it be that you have a custom module in your menu (maybe FFGL) that crashes when the project is cleared?
When you select a module and then press Ctrl+Up, it tries to replace the module with the previous one in the menu. Could it be that you have a custom module in your menu (maybe FFGL) that crashes when the project is cleared?
Re: Heap corruption 2.5
No, even if I add a null, select it, new scene, ctrl up, a new node appears, new project, crash. Disabling all my module paths, it still crashes.
Re: Heap corruption 2.5
Ok, hopefully we can fix this for our next version. I think the bug is that it's replacing the module in the new scene (incorrectly) and trying to connect it to the original scene.