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
+9.1k Golang : does not implement flag.Value (missing Set method)
+15.1k nginx: [emerg] unknown directive "ssl"
+7k Restart Apache or Nginx web server without password prompt
+21.7k Golang : How to reverse slice or array elements order
+30.9k Golang : Calculate percentage change of two values
+8.1k Golang : Qt splash screen with delay example
+19.4k Golang : How to Set or Add Header http.ResponseWriter?
+11k Golang : How to determine a prime number?
+13.2k Golang : Date and Time formatting
+12.1k Golang : Simple client-server HMAC authentication without SSL example
+10.2k Golang : Embed secret text string into binary(executable) file
+10.7k PHP : Convert(cast) bigInt to string