[0.12.12] [cube] pcall behavior changed

[orzelek]

There's definitely something wrong with the Linux release build. We're looking into it.

This particular issue doesn't happen on the Windows release build (which is what I've been testing with).

Might be unrelated - I got an error posted for RSO when one of files fails to parse.
I can't reproduce it on my windows machine but there was some strange part in there (value was written as 0,4 not 0.4).
Is it possible it's related to this?

[Rseding91]

There's definitely something wrong with the Linux release build. We're looking into it.

This particular issue doesn't happen on the Windows release build (which is what I've been testing with).

Might be unrelated - I got an error posted for RSO when one of files fails to parse.
I can't reproduce it on my windows machine but there was some strange part in there (value was written as 0,4 not 0.4).
Is it possible it's related to this?

Yes. What would normally give a nice "script error" output and exit to the main menu is causing a full crash on the Linux release build.

[orzelek]

There's definitely something wrong with the Linux release build. We're looking into it.

This particular issue doesn't happen on the Windows release build (which is what I've been testing with).

Might be unrelated - I got an error posted for RSO when one of files fails to parse.
I can't reproduce it on my windows machine but there was some strange part in there (value was written as 0,4 not 0.4).
Is it possible it's related to this?

Yes. What would normally give a nice "script error" output and exit to the main menu is causing a full crash on the Linux release build.

It's a bit different here. It doesn't error out at all on windows build. It was parsing till now without any errors at all. And it still is for windows build.
It produced syntax error on linux(my assumption) thats visible here:
https://forums.factorio.com/forum/vie ... 94#p113909
As far as I can see that code was there from August.

[cube]

Thanks for the report (and all the ones I marked as duplicate :-) ), these problems should be fixed for 0.12.13.

I changed our build to use link time optimizations, but it looks that the toolchain still has some bugs :-). In this case it caused the 0.12.12 to immediately terminate after an exception was thrown instead of catching it properly.