Open missinglink opened 2 years ago
This was caused by passing a reference to another go routine via a chan *geos.Geometry
.
Refactoring the code to do all operations within the scope of a single function avoided the issue.
After playing with the lib a little more it seems that it's not thread-safe. Does anyone know if that's the case?
I noticed a few years ago that spatialite
migrated from GEOS
to RTTOPO
because it offered improved thread-safety.
Hi,
Using this library under heavy load I received the following error. Any info about the meaning of "Pure virtual function called" or hints on where to look in the code to fix this much appreciated 🙏
possibly related: https://github.com/paulsmith/gogeos/pull/29