Row-value UPDATE statements inside of TRIGGERs cause segfaults, memory leaks,
and/or assertion faults.  Example:

<blockquote><pre>
CREATE TABLE t1(a,b,c);
INSERT INTO t1 VALUES(1,2,3);
CREATE TABLE t2(x);
CREATE TRIGGER r2 AFTER INSERT ON t2 BEGIN
  UPDATE t1 SET (a,b,c)=(SELECT 4,5,6);
END;
INSERT INTO t2 VALUES(1);
SELECT * FROM t1;
SELECT * FROM t2;
</pre></blockquote>

This problem has existed ever since row value were added in version 3.15.0,
about two months ago.