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
+17.2k Golang : How to generate QR codes?
+7.6k Golang : Example of custom handler for Gorilla's Path usage.
+21.3k Golang : Convert(cast) string to rune and back to string example
+5.9k Golang : Struct field tags and what is their purpose?
+18.2k Golang : How to log each HTTP request to your web server?
+6.4k Linux/Unix : Commands that you need to be careful about
+7.6k Golang : Get YouTube playlist
+27.9k Golang : dial tcp: too many colons in address
+40.4k Golang : UDP client server read write example
+14.6k Golang : Simple word wrap or line breaking example
+5.8k Fix yum-complete-transaction error
+11.8k Golang : Fuzzy string search or approximate string matching example