3 ms·
the linked issues are quite interesting, why does go have to page in so much memory for the GoString? Is this for some sort of optimization? https://github.com/
by vsgherzi 10mo ago
the linked issues are quite interesting, why does go have to page in so much memory for the GoString? Is this for some sort of optimization? https://github.com/mullvad/mullvadvpn-app/pull/6727 https://github.com/mullvad/mullvadvpn-app/pull/6727
if anyone else is more familiar with go (I only really do rust) is there no solution to preventing stack smashing on goroutines? https://github.com/mullvad/mullvadvpn-app/pull/7728 https://github.com/mullvad/mullvadvpn-app/pull/7728
I understand that go routines have a smaller stack size (the whole green thread problem) but there's no way to fix this?
- Rawa 10mo agoIt was solved in another PR by using an alternate stack by setting the flag SA_ONSTACK.