Oh, so this is the reason my editor is using 10GB ram and crashes 10 times per day.

And it wont be fixed. Nice!

Woah. Way to drive your users away to Unreal or other engines.

I will also add, this is what makes, me and other professionals know that Unity is not serious engine anymore when it comes to people making and releasing games with it... If you where, you would been working with us NOT against us... I will continue being blunt about issues, no matter how mad you are at people like me for being blunt. I report bugs and wait months for a reply only for a answer that doesn't actual help, and then we get nonsense like this... This is a critical issue.... I would love to know why Unity thinks this is not critical... For any professional who has worked with Unity terrain knows this is certainly top of the list having crashing issues , and handling memory management... Memory Management is on top of the list and one reason Unity can't seem to handle larger projects either, I have said this for years and been ignored and now we are seeing others who are finally working with them to, finally seeing these issues coming to light....... "wake up Unity and listen or we will continue using other engines and dumping Unity for our projects.."/

Unity go make games, then you will see HOW much its worth fixing..... Making tech demos's is not making a game.....

So sick of people like myself and others who make games for a living and been contractors since Unity 2, to be ignored..... non destructive is the type of tools that will only get bigger so we need to be able to use 4k stamps.. as mention this is an easy fix.. SO why not hire someone to fix it for you if you are to lazy or just don't know how.. Not sure how else I can be blunt about this... But this is why I used Unreal for 20 yrs also and use for my current game, I had to many clients where we would hit brick walls from Unity ignoring critical issues.

as Rowlan said: "it's sane to use 4K stamps on a 4K terrain. It also works just fine. It's just that the memory management needs to be dealt with with stamps that are not in use."
This is making the editor crash just by adding stamps to the project. You need to fix this!

You can't simply ignore a consistent editor crash on a completely reasonable use case! Unity, fix this already! :-(

Wow, pretty wild to consider this not worth fixing. Was the bug not understood?

That's the thing, you don't have to be "utilizing" the stamps at all. If they are in the project, crash. Closing this as won't fix makes me wonder what you actually consider worth fixing, since you can simply download an asset pack of stamps from the store and crash Unity by selecting a terrain once they are installed.

Basically, you're saying Unity can only have a few stamps in the project because no one over there tested with more than a few of them in a project and you don't ship games anyway, so have no idea how people use Unity and don't care if it crashes all the time. In a real project in production, you might have hundreds of stamps there for creating you environment, just like you might have hundreds of textures in your game but not all of them used at once.

Also, the fix to MV to handle this case was like 10 minutes of work, so quit making excuses.. I'd fix the code myself, but I'm sure QA would just bounce it.

This is a critical bug. I have no idea how a major bug like this can be categorized as not critical and "won't fix". The bug makes you literaly run out-of-memory and therefore crashing the editor by selecting the terrain gameobject in an otherwise empty scene. Sorry but classifying this as "won't fix" is madness.