Solve problem with no stack trace

I made an editor type app in version 14.20.0. It requests data about quay walls from an API, this data is a few MB. In the local development version it works perfect.

In the published editor type app it often does not work as I expect. The error report says:
No stack trace available since the job was killed unexpectedly. This usually happens when:

  • too much memory was used (most likely)
  • too much disk space was used

Any advice on how to solve this problem?

In another app (tree type, v14.16.1) almost the same functionality is implemented, but without putting the data in a params table. That requires multiple calls to the API to set a few other params that are used to filter the data for plots. That works without issue in the development and the published version

Update: the data is received alright from the API and read in a table in params.
I tried a few different objects, it seems that somewhere between 950 rows and 1700 rows the error starts to occur.

Hi Thomas, you rightfully identified that this is a resource problem (disc or memory). Unfortunately the process crashes then and we don’t have a traceback to show.

Here are a few threads that can help you identify where the problem is and how to address it:

kind regards,
Matthijs