This query has at about 19kB:

create tab_out as
select
x1*(0.019613279029726982)+x2*(0.018225347623229027 )+...+x1000*(0.037470344454050064)
as zm1,
from tab_in

After running it database server crashes and after auto restart I have
in log:

061106 11:42:12 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.0.22-max-log' socket: '/var/run/mysql/mysql.sock' port:
3306 MySQL Community Edition - Experimental (GPL)

Number of processes running now: 0
061106 15:56:03 mysqld restarted
061106 15:56:04 InnoDB: Started; log sequence number 0 43655
061106 15:56:04 [Note] Recovering after a crash using kamilajs-bin
061106 15:56:10 [Note] Starting crash recovery...
061106 15:56:10 [Note] Crash recovery finished.
061106 15:56:10 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.0.22-max-log' socket: '/var/run/mysql/mysql.sock' port:
3306 MySQL Community Edition - Experimental (GPL)

When I've changed this query to:

create tab_out as
select
x1*(0.019613279029726982)+x2*(0.018225347623229027 )+...+x500*(0.037470344454050064)
as zm1a,
x501*(0.019613279029726982)+x2*(0.0182253476232290 27)+...+x1000*(0.037470344454050064)
as zm1b,
from tab_in

everything is OK. Is there some kind of limit on variable definition
length? And if - why mysql crashes not telling me what is the problem?
How to fix it?

Thank you for any suggestions.

Best regards.