Anyone else experienced any issues with NSObjects never being deallocated on macOS? This seems like a very serious issue as it means any application that uses NSObjects is exposed to memory leaks. I created an issue to track but it would be great to know if anyone else experiences this behavior. If so it would be great to upvote to gain exposure 🙂
https://youtrack.jetbrains.com/issue/KT-33780
o
olonho
09/09/2019, 8:44 PM
Note that
Copy code
autoreleasepool {
NSObject() // memory footprint steadily grows while executing this loop
}
fixes your problem.
s
Sam Schilling
09/09/2019, 9:36 PM
@olonho thanks for the help. Followed up with a question on the bug track 🙂