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
+10k Google Maps URL parameters configuration
+5k Golang : How to verify input is rune?
+13.2k Golang : Overwrite previous output with count down timer
+6.1k Golang : Array mapping with Interface
+3.9k MariaDB/MySQL : Form select statement or search query with Chinese characters
+5.5k Golang : Calculate diameter, circumference, area, sphere surface and volume
+6.7k Golang : How to execute code at certain day, hour and minute?
+17.1k Golang : Implement getters and setters
+8.9k Golang : Channels and buffered channels examples
+4k HTTP common errors and their meaning explained
+6.5k Golang : What fmt.Println() can do and println() cannot do
+9.7k Golang : Fix - does not implement sort.Interface (missing Len method)