Fix fatal error: evacuation not done in time problem


4617 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

+30.7k Get file size in Go


+4.3k PHP : Send HTML email


+12.2k Golang : Tutorial on loading GOB and PEM files


+17.5k Golang : Clearing slice


+14.5k Golang : convert string or integer to big.Int type


+4.7k Golang : Function as an argument type example


+10k Golang : Byte format example


+7k Useful methods to access blocked websites


+5.4k Golang : Calculate pivot points for a cross


+32.1k Golang : How to check if slice or array is empty?


+3.7k JQuery : Calling a function inside Jquery(document) block


+4.1k Golang : Issue HTTP commands to server and port example