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
+10.3k Golang : Fuzzy string search or approximate string matching example
+13.7k nginx: [emerg] unknown directive "ssl"
+17.2k Golang : Read binary file into memory
+15.4k Golang : read gzipped http response
+10k Golang : Concatenate (combine) buffer data example
+16.3k Golang : [json: cannot unmarshal object into Go value of type]
+10.7k Golang : Clean formatting/indenting or pretty print JSON result
+4.9k Golang : Measure execution time for a function
+9k Golang : Random Rune generator
+45.5k Golang : Convert int to byte array([]byte)
+14.5k Golang : Loop each day of the current month example
+20.6k Golang : Print leading(padding) zero or spaces in fmt.Printf?