Forest editor crash on object placement

!@#$%!!!!

This bug has been around since 0.9.x, since the forest editor was re-done.
Cannot place any object - or randomly some objects - without a CTD.
Doesn't matter if there's a bunch used already, or if you do other things first.
Doesn't matter how many objects are in the map. This happens a LOT.

To the point I can no-longer place anything in the map, and for now am considering shelving my city map permanently until the bug is fixed (because, I can't place anything).

This bug first reared it's head in Roane County Tennessee development, but I was always able to get around it after trying to move another forest object around (there-by accessing the files that store them and having them ready), now I cannot. Maybe it's shared privileges this game does not like, as some may be open in a text editor (because the stupid forest brush FAILS to delete most anything I try to delete!!!).
It's very hard to get a nice map made when nothing is working in the forest brush.

Can't upload the log it's 71mb. I don't know how a log gets to 71mb but whatever.

The game doesn't give a specific error anyways, so take a piece of blank paper and pretend it's the log.
What's the log supposed to do anyways? It's been next to useless for editor-related errors since 0.10 or 0.11

 

How about if you rename/remove texture of said object that you try to replace, so that game does not find the texture, does it crash or place beautifully orange object with words on it?

What I have had happen with editor was that when I did click to place an object, I got instantly a crash, but with texture removed it placed object just fine. Path of the object was perfectly right, except it did reside inside a zip file of JRI, it should of worked, it should work from the path despite being in zip, but no, only did work when I removed texture file.

If your crash disappears by removing texture, then it would reveal that this crash is by the game somehow messing up it's own paths in memory or some other place, but at least it would give place in code to examine closer.

However it could be that there is some other part of code that causes crash in your case, either way testing with renaming texture file would be easy to do.

Just thought that came to me all of sudden.