Hi,

The usage of SUSPEND in the procedure has been corrected.

I have not, unfortunately, been able to reproduce the error. :-( I
tried writing a simple procedure, including a SUSPEND statement, and
executing it (with "execute procedure") 10000 times (committing after
each call), on each of 3 simultaneous connections. It had no effect
on memory usage of the FireBird server, and no crash.

Thanks,
Riaan

--- In ib-support@y..., Daniel Rail <daniel@a...> wrote:
> When using "execute procedure", don't use "SUSPEND" in the stored
> procedure. SUSPEND is used to return values when using the stored
> procedure in a SQL-DML statement(i.e. SELECT). This could be a bug
> in the database server for not recognizing the error and raising a
> friendlier error message, instead of crashing the server. It is a
> bug if you can reproduce it as many times as you want. Try
> creating another database and try to reproduce it, I suggest you
> use a test computer for this. Report back here with your results.