-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WE Crashes Minetest when Loading (dot)we File #67
Comments
Seems like something got corrupted somewhere - can you upload the schematic for testing? As a temporary workaround until this is fixed, try a build without LuaJIT. |
Minetest engine, GitHub commit, 2014_12_10, fb80a7c111 Requested schematic, same build, 2 files (1 LuaJIT, 1 without), default nodes: Without LuaJIT - we_no_luajit.we I compiled Minetest without LuaJIT (-DDISABLE_LUAJIT=1) and another instance with LuaJIT. In the LuaJIT instance I //saved we_luajit and then tried //loading it in another world - Minetest crashed with the same errors. Then I copied both worlds into the **non-**LuaJIT instance, //saved we_no_luajit, and successfully //loaded it into the other world. While still in the **non-**LuaJIT, I then tried //loading the we_luajit file and it worked. Following that, I copyied we_no_luajit.we into a world in the LuaJIT compiled instance of Minetest and Minetest crashed when I tried to //load the schematic with the same error. So it would seem that the //save process works in both **non-**LuaJIT and LuaJIT compiled instances of Minetest but the //load process is fubared. While using WorldEdit in the **non-**LuaJIT instance, these errors came-up in the terminal:
I hope this helps. |
I can confirm this bug also. Another example schematic that crashes Minetest (with the same error/backtrace as LazyJ initially reported; I use LuaJIT also): http://digitalaudioconcepts.com/vanessa/hobbies/minetest/oldspawn.we In my case, I was simply trying to reload the schematic into another area in the same world from which it was just saved a minute or so prior (I was moving the "spawn building" in one of my worlds). |
I think this should be fixed in 04fdf92 - give it a try! Your test cases were very useful - for some reason |
WorldEdit GitHub commit, 2014_10_24, fb49cc4
MIneteset engine, GitHub commit, 2014_12_09, dcc48976ce
I tried three times to transfer a small build (286 nodes) from one singleplayer world to another using //save and //load. I saved the build (//save shack), then copied the "shack.we" file to the schems folder of another singleplayer world, and then tried to place the build in that world using "//load shack". At this point, Minetest crashed each time.
Here are error messages from the terminal output:
The text was updated successfully, but these errors were encountered: