mattn / go-sqlite3 / 1037

52%

master: 54%

Pull #790

travis-ci

Make sqlite3.Open thread safe

* sqlite3_open_v2 implicitly calls sqlite3_initialize
* sqlite3_initialize is not thread safe in the prologue
* concurrent calls of sqlite3.Open even on different files
  may trigger mutex initialization race and crash
* Fix: use go channel with a single message in it as a barrier
  letting only single-threaded sqlite3_open_v2 for the first time
* Reproducibility: very low, couple hours of concurrent sqlite3.Open calls
  trigger a single crash

7 of 7 new or added lines in 1 file covered. (100.0%)

970 of 1877 relevant lines covered (51.68%)

1432402.46 hits per line