You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Operating system or device, Godot version, GPU Model and driver (if graphics related):
Godot 3.0 (e8ad604), macOS Sierra 10.12.6
Issue description:
When exporting project from command line, translation.csv reimport causes weird behaviour (export loop followed by segfault) afterwards, as if the memory got corrupted. There is no segfault when reimport is done when you open the project in the editor without immediately exporting.
EditorProgress calls Main::iteration which calls MessageQueue::flush
which may result in _fs_changed being called again. This fixes the loop
Godot enters in such case.
Fixesgodotengine#11189
Operating system or device, Godot version, GPU Model and driver (if graphics related):
Godot 3.0 (e8ad604), macOS Sierra 10.12.6
Issue description:
When exporting project from command line, translation.csv reimport causes weird behaviour (export loop followed by segfault) afterwards, as if the memory got corrupted. There is no segfault when reimport is done when you open the project in the editor without immediately exporting.
Steps to reproduce:
git clone -b translation-bug https://github.com/endragor/etc2bug.git translationbug cd translationbug godot --export Android test.apk
The text was updated successfully, but these errors were encountered: