Fix fatal error: evacuation not done in time problem


4514 views 25th September 2014


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

+32.4k Golang : Strip slashes from string example


+10k Swift : Convert (cast) Float to String


+32.2k Golang : convert(cast) bytes to string


+13.4k Golang : Intercept Ctrl-C interrupt or kill signal and determine the signal type


+6.3k Gogland : Where to put source code files in package directory for rookie


+30.3k Get file size in Go


+9.8k Golang : Send data to /dev/null a.k.a blackhole with ioutil.Discard


+7k Golang : Gaussian blur on image and camera video feed examples


+9.2k Golang : Web routing/multiplex example


+4.9k Golang : Find the longest line of text example


+22.5k Golang : Call function from another package


+4k Unix/Linux/MacOSx : How to remove an environment variable ?