> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/writebackextreme/troubleshooting-and-faq/extension-errors/log-states-allowed-memory-size-of-xxx-bytes-exhausted.md).
# Log states: Allowed memory size of xxx bytes exhausted
When this happens, WriteBackExtreme is attempting to load too much data. The extension retrieves records in batches of 1,000 until all rows are fetched. If each row contains a large amount of data or the table has many columns, this process can exhaust the available memory.
The best solution is to limit the amount of data being queried. Ask yourself: *Do I really need to load this much data?* Often, a slimmer table can serve the same purpose—and will perform significantly better than a large table packed with heavy rows.
If reducing the dataset is not an option, there are two alternatives:
1. **Decrease the number of records loaded per batch** (default is 1,000).\
**Note:** This setting applies to *all* schemas.
You can do this by navigating to the 'Chunk Size' setting within the advanced configuration, and lowering it:
2. Increase the memory limit by altering the `wbe.config.toml` file like so:
Note that the indentation in wbe.config.yaml matters! To apply the new memory limit, please restart WriteBackExtreme.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.infotopics.com/writebackextreme/troubleshooting-and-faq/extension-errors/log-states-allowed-memory-size-of-xxx-bytes-exhausted.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
