[0.3.2][0.5.1][Not fixed] Map Editor Segfaults
[0.3.2][0.5.1][Not fixed] Map Editor Segfaults
Hi,
try this:
1) Open map editor, generate map 400x400 in size (has to be large enough for large enough amount of enemies).
2) Remove all enemy spawners and their towers. Nicely one by one, with your 'x' key.
3) Place your player.
Then the game receives the Segmentation Fault error. Looks like a bad pointer, eh?
system: Archlinux, 32-bit
try this:
1) Open map editor, generate map 400x400 in size (has to be large enough for large enough amount of enemies).
2) Remove all enemy spawners and their towers. Nicely one by one, with your 'x' key.
3) Place your player.
Then the game receives the Segmentation Fault error. Looks like a bad pointer, eh?
system: Archlinux, 32-bit
Last edited by Dr.Eddy on Tue Jun 18, 2013 7:36 am, edited 2 times in total.
Re: Map Editor Segfaults
aaa that happen to me too. I though it was something random first,but now I see I took same steps.
Win7 64bit
Win7 64bit
Test mode
Searching Flashlight
[WIP]Fluid handling expansion
[WIP]PvP gamescript
[WIP]Rocket Express
Autofill: The torch has been pass to Nexela
Searching Flashlight
[WIP]Fluid handling expansion
[WIP]PvP gamescript
[WIP]Rocket Express
Autofill: The torch has been pass to Nexela
Re: Map Editor Segfaults
I guess that this is already repaired, can you check it?
Re: [Probably fixed] Map Editor Segfaults
Yea I still get Factorio.exe has stop working alert.
Test mode
Searching Flashlight
[WIP]Fluid handling expansion
[WIP]PvP gamescript
[WIP]Rocket Express
Autofill: The torch has been pass to Nexela
Searching Flashlight
[WIP]Fluid handling expansion
[WIP]PvP gamescript
[WIP]Rocket Express
Autofill: The torch has been pass to Nexela
Re: [Probably fixed] Map Editor Segfaults
No, it's not fixed. It still segfaults, but now it's a bit worse.
It takes some time for it to come down. Previously, it was instantaneous, now it freezes for a while, grabs all memory it can and then it segfaults. My system started swapping real bad!
It takes some time for it to come down. Previously, it was instantaneous, now it freezes for a while, grabs all memory it can and then it segfaults. My system started swapping real bad!
Re: [0.3.2][0.5.1][Not fixed] Map Editor Segfaults
Bumping this thread as this is still valid bug report. Which is quite sad.
Re: [0.3.2][0.5.1][Not fixed] Map Editor Segfaults
This thread was forgotten when we were preparing 0.4.x and 0.5.x. Sorry for that and thanks for bumping it. I have managed to reproduce the problem and this is now fixed. The fix will be shipped either in 0.5.2 (if there is such a release) or 0.6.0.
Re: [0.3.2][0.5.1][Not fixed] Map Editor Segfaults
@ kovarex - can you reproduce? It would be nice if you said that you can't, so it would be obvious that you have to rely on Dr.Eddy's testing.
BTW: The editor really isn't game-criticalDr.Eddy wrote:Bumping this thread as this is still valid bug report. Which is quite sad.
Re: [0.3.2][0.5.1][Not fixed] Map Editor Segfaults
Dude, stop this madness. Do you really want to go there? This is like some kind of holy war against me.MF- wrote:@ kovarex - can you reproduce? It would be nice if you said that you can't, so it would be obvious that you have to rely on Dr.Eddy's testing.
And BTW: have you noticed one other guy also noticed the bug and just today one of the devs also reproduced the bug and fixed it?
Re: [0.3.2][0.5.1][Not fixed] Map Editor Segfaults
Your recent posts and demands were extremely aggressive compared to the rest of the messages here.Dr.Eddy wrote: Dude, stop this madness. Do you really want to go there? This is like some kind of holy war against me.
There is just no reason for saying that in a bug report. It definitely doesn't put it in the priority box.
(Some of them looked a lot like these to me: "the devs are sooo incompetent" and "this must be fixed because it bothers **ME**!")
Some people completely ignore such posts, some reflect the aggression back, resulting in... agreed, holly war is a good description.
I call this war over
AH. I totally missed those two posts. I have no idea how that happened. Congrats on having it fixedAnd BTW: have you noticed one other guy also noticed the bug and just today one of the devs also reproduced the bug and fixed it?