ST_MakeValid: Segmentation fault terminated by signal 11

[postgistrac]

The following query results in a segfault:

SELECT st_makevalid(st_geomfromtext('MULTIPOLYGON(((37.541915 -150.1016354,-20.1565008 144.4184397,-122.3686927 66.9350039,213.6988278 -165.2224247,204.8992242 214.3221174,214.0589173 49.0659876,-182.6551982 -112.8902799,176.1138463 -170.5609524,95.724424 -20.2676847,92.2292318 23.8341385,92.2292318 -29.9294218,92.2292318 83.664327,-129.7154775 -132.625674,203.6634646 -144.8588469,152.9831767 -90.6833667,58.6129853 -85.4405783,23.6610626 -19.0319252,23.8165922 64.9110642,154.960398 -113.8718603,117.0310869 56.5946351,-125.2518334 56.5946351,-193.0733564 -203.7728494,37.541915 -150.1016354)))', 4326));

POSTGIS="2.0.1 r9979" GEOS="3.3.5-CAPI-1.7.5" PROJ="Rel. 4.7.1, 23 September 2009" LIBXML="2.6.26"

Error log:

2013-07-07 04:00:09 CEST: LOG: server process (PID 30894) was terminated by signal 11: Segmentation fault
2013-07-07 04:00:09 CEST: LOG: terminating any other active server processes
postgres db209789_2 2013-07-07 04:00:09 CEST: WARNING: terminating connection because of crash of another server process
postgres db209789_2 2013-07-07 04:00:09 CEST: DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
postgres db209789_2 2013-07-07 04:00:09 CEST: HINT: In a moment you should be able to reconnect to the database and repeat your command.
2013-07-07 04:00:09 CEST: WARNING: terminating connection because of crash of another server process
2013-07-07 04:00:09 CEST: DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2013-07-07 04:00:09 CEST: HINT: In a moment you should be able to reconnect to the database and repeat your command.

2013-07-07 04:00:10 CEST: WARNING: terminating connection because of crash of another server process
2013-07-07 04:00:10 CEST: DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2013-07-07 04:00:10 CEST: HINT: In a moment you should be able to reconnect to the database and repeat your command.

2013-07-07 04:00:10 CEST: LOG: all server processes terminated; reinitializing
2013-07-07 04:00:11 CEST: LOG: database system was interrupted; last known up at 2013-07-07 03:59:44 CEST
2013-07-07 04:00:12 CEST: LOG: database system was not properly shut down; automatic recovery in progress
2013-07-07 04:00:24 CEST: LOG: redo starts at 2D6/E80087E8
2013-07-07 04:00:35 CEST: LOG: unexpected pageaddr 2D6/DEA56000 in log file 726, segment 233, offset 10838016
2013-07-07 04:00:35 CEST: LOG: redo done at 2D6/E9A55F20
2013-07-07 04:00:35 CEST: LOG: last completed transaction was at log time 2013-07-07 04:00:00.033718+02
2013-07-07 04:00:38 CEST: LOG: autovacuum launcher started
2013-07-07 04:00:38 CEST: LOG: database system is ready to accept connections

[robe]

My install returns:

POSTGIS="2.1.0rc1dev r11637" GEOS="3.4.0dev-CAPI-1.8.0 r0" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.10.0, released 2013/04/24 GDAL_DATA not found" LIBXML="2.7.8" LIBJSON="UNKNOWN" RASTER PostgreSQL 9.3beta2, compiled by Visual C++ build 1600, 32-bit

NOTICE:  LWGEOM_GEOS_nodeLines(): TopologyException: found non-noded intersection between LINESTRING (94.1104 0.0976963, 92.2292 -0.670284) and LINESTRING (92.2292 -0.670284, 92.2292 -28.3531) at 92.229231799999994 -0.67028434840479534

I think this issue has already been fixed in 2.1.0 and 2.0.4 about to be released in ticket #2307. Also you are running an obsolete GEOS. Might want to upgrade to GEOS 3.3.8 or 3.3.9 which will be out soon. Or even GEOS 3.4.0 which will also be out soon.