Fix fatal error: evacuation not done in time problem
Encounter one of the strangest error messages in Go today regarding evacuation. Now, what the heck "evacuation" has to do with programming language ? Apparently it has something to do with locks.
This error message :
"fatal error: evacuation not done in time"
is caused by accessing a map from multiple go-routines and ....map is not thread-safe.
Solution :
Check if the RLock or Lock is in proper place. Might need some fine tuning through trial and error.
p/s : This solution is applicable to the error message fatal error: bad state as well.
By Adam Ng
IF you gain some knowledge or the information here solved your programming problem. Please consider donating to the less fortunate or some charities that you like. Apart from donation, planting trees, volunteering or reducing your carbon footprint will be great too.
Advertisement
Tutorials
+16.2k Golang : How to check if input from os.Args is integer?
+10.7k Golang : How to delete element(data) from map ?
+21k Golang : Convert PNG transparent background image to JPG or JPEG image
+9.4k Golang : How to find out similarity between two strings with Jaro-Winkler Distance?
+6.5k Unix/Linux : Use netstat to find out IP addresses served by your website server
+11.7k Use systeminfo to find out installed Windows Hotfix(s) or updates
+21k Golang : Underscore or snake_case to camel case example
+26.8k Golang : How to check if a connection to database is still alive ?
+10.7k Golang : Create matrix with Gonum Matrix package example
+37.7k Upload multiple files with Go