Issue applies only on the different selection tool:

• Place Fill Origin
• Set Position of Line build helper

Good find, seems it's already resolved in the pre-release candidate though.
If I had to guess, it's the same issue as T2401, seems I missed this messed up block icon colour back then.

Thank you for reporting but we already have this one in queue. Merging tasks together.

Could you post a screenshot of said effect? Press F5 in-game to take one, the file should be in your ./StarMade folder, drag and drop the file in phabricator's message box to upload it here.
I believe I know what you're talking about, but that should have been fixed before.

Should hopefully be easy to see, I believe I saw something like this happen already to some of my PD turrets, not 100% sure as that was in SP.

Im getting a LOT of these recently now that Ive started back into fighting other ships and testing. Retry is a temporary fix if it doesnt outright crash.

Could you upload your logstarmade.0.log after reproducing this issue? It's in your ./StarMade/logs folder, just drag and drop the file into phabricator's message box to upload it here.
0.199.634 is still a dev build and any of the test servers running on it are down it seems, so it may not be an issue on your end but logs should say more about that.

Duplicate, merging tasks.

i logged onto the server i play on after playing on sp and i was almost constantly getting the error (we where under attack) so here is a new set of logs. also cannon shots and missiles froze in mid air after and during the error.

I was able to reproduce it using the process above on a new world, this time with missiles and cannons/cannon/explosive effect. I am uploading the world and logs, one of the ships i was able to reproduce it with is in sector 50, 500, 500, the turrets are cannon turrets.

Nothing to add.

Duplicate for T2372, was fixed in a dev build although that fix is not in a public version yet.

Old bug that was tackled in another task, might still happen though but that will be looked at in the other task.

Duplicate of T727, due to the inconsistent behavior though I'm inclined to put it in queue for it to be fixed.

Don't think this is a bug, just an incomplete mechanic. The part you put in bold would be the only thing that requires "fixing".

The turrets behave fine, as they're just aiming for missiles that have stalled. The real issue is that some missiles have stalled for some reason, if you're able to consistently reproduce this, please upload your logstarmade.0.log after encountering missile stalling. Say something in chat too like "missiles are stalling" so it's easier to find in logs.

Duplicate, merging tasks.

Well, can't reproduce it but at this point I'm not really surprised...These GL Exception issues happen seemingly random for players or if you're able to reproduce it consistently, it seems only you can do that and anyone else is just fine.
Might depend on GPU drivers but as both you and me are using Nvidia, I'm not entirely sure what's happening in your world compared to my test setup.

Hopefully I'm able to reproduce. If you hold F1 + F2 at the same time, you can often force a GL_Invalid value to happen in case you want to give it a shot.

Good find!
Updating information a bit, putting in queue.

Awesome! Found an existing of the break off issue but it's a bit outdated. Will merge the tasks together and update the original one.

Yes, disabling break off appears to fix this issue, thanks for the feedback :)

Did you see that happen in the current release, or the latest devbuild? If it's one of the dev builds, it's an unwanted side effect of the fix for T161

Yes it is.

In order to get some more information about this crash, we need you to upload your log file here. The logfile we need is named logstarmade.0.log and is located in your ./StarMade/logs directory.
Reproduce this problem, and after that crash, upload that logfile (make sure to upload that file before restarting the game, or else the file will be overridden).
Drag and drop the file in the comment box here on Phabricator to upload it.

Apologies on the delay there

Going to main menu and back in-game several times in the same session will indeed result in a memory build up, although that should steadily decline after a while but usually at a too slow pace to help.
Frequently alt tabbing can make the GC go lazy too often and could also take a while for it to recover completely.

@Lunchbox and @The_Onion
Can any of you upload a blueprint of the ship + thing docked to it that causes it? And/or provide very clear steps to reproduce for a simple example?

Interesting, found this:

[2017-06-07 09:59:12] Exception in thread "pool-2-thread-1" 
[2017-06-07 09:59:12] java.lang.ArrayIndexOutOfBoundsException: 10485763
[2017-06-07 09:59:12] 	at org.schema.game.common.data.explosion.ExplosionDataHandler.a(SourceFile:162)
[2017-06-07 09:59:12] 	at obfuscated.adN.run(SourceFile:313)
[2017-06-07 09:59:12] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
[2017-06-07 09:59:12] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[2017-06-07 09:59:12] 	at java.lang.Thread.run(Unknown Source)

which is about a minute after your force-save started.

I see. Main issue is then that the "Set price to Buy" and "Set price to Sell" for the shop owner (only the shop owner gets this anyway), should be switched around when it comes to function.
We might as well give them the exact same name as in the Trade Order one

Yeah, can reproduce fine now, probably messed up and forgot that '+ protected' isn't persistent between shutdowns.

Interesting details, missile targeting changed quite a bit but this could give us clues of what's happening in another issue. Merging them together.

Merging this issue into another one.

Well I can reproduce some of it, but doesn't sound as severe as you describe it.
Basically anything from a single tick can only apply either planet core damage, or block damage.

Should have been caused by a NaN exception upon undocking. Shootout rails pointing towards each other and including pick up rails close by would have triggered that.
That's fixed, or at least most cases are fixed...any remaining issue will be handled in another task. Merging them together now

Thank you for the report though we already have one, merging tasks together.
There's more information if needed in the merged task, it will be fixed for the next public version.

T1870 could perhaps be related although sounds like a completely different cause.

Putting in queue but not sure if it contains enough info to be fixed. Another entity had it too so will include info if needed.

Depends on the amount of blueprints you have (and also on the server I believe). It freezes, but as long as you don't really do anything it will get through.
Would merge this one with T2176 but wouldn't mind your logstarmade.0.log after crashing to see if it's the same issue or some sort of exception that pops up first.

Valid issue, but it's another consequence of an existing task, merging them together.

Server Log file:

The NOT block can't be used to send rail changes anymore. A true or false signal doesn't do anything when trying to set the rail type or change its orientation.