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
+4.5k Golang : GMail API create and send draft with simple upload attachment example
+18.6k Golang : Read a text file and replace certain words
+2k Golang : micron to centimeter example
+2.4k Golang : Shortening import identifier
+6.1k Python : Convert IPv6 address to decimal and back to IPv6
+13.2k Golang : Set and Get HTTP request headers example
+4.5k Golang : GTK Input dialog box examples
+6.4k Golang : Read file and convert content to string
+1k Golang : How to check if a website is served via HTTPS
+2.6k nginx : force all pages to be SSL
+1.1k Golang : What fmt.Println() can do and println() cannot do
+5k Golang : Forwarding a local port to a remote server example
