You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the list of batches is very large (the project I tested on had 10k+ batches), the observed behavior is the tab crashes due to an out of memory error or the batches list table reverts to a "no results" state after showing partial results.
I suspect the following things are happening:
The plugin is requesting all of the page for batches list during initialization instead of requesting a handful and continuing the request as the user pages through the list.
The batch info that the plugin requests are stored in memory, which can grow very large and cause OOM errors.
Due to the volume of requests sent in a short period of time, the server returns with a 429 error.
The text was updated successfully, but these errors were encountered:
If the list of batches is very large (the project I tested on had 10k+ batches), the observed behavior is the tab crashes due to an out of memory error or the batches list table reverts to a "no results" state after showing partial results.
I suspect the following things are happening:
The text was updated successfully, but these errors were encountered: