GEOS 3.3.7 when used, results is fatal issues, broken db connections and even crashed VPS

While we have no idea why exactly this happens, when the module is trying to use latest GEOS 3.3.7 on a system with latest PHP-FPM 5.3.21, it causes very serious problems, like discussed in the thread: #1913488: GEOS PHP extension causes Aborted connections with (Unknown error) reported on some URLs only

No idea if there is anything you could do about it, since it could be GEOS 3.3.7 and/or PHP-FPM 5.3.21 related, but just want to let you know that such problem exists, so we had to disable previously by default enabled GEOS support in BOA.