> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/troubleshooting/performance_issue_troubleshooting.md).

# Performance issues troubleshooting

Performance issues may be related to the limitations of your computer's hardware or software. The Emedgene platform needs 2 Gb of free allocated memory to run properly.

If you are experiencing slower loading times or disruptions in service, please consider the following steps to improve your experience:

1. Check for Background Tasks:

Task Manager (Windows) or Activity Monitor (macOS): Open these tools to see if any background processes are consuming excessive memory. End any unnecessary tasks.

2. Free Up Memory:

* Close Unnecessary Apps: Close other applications that might be using memory, even if they're not actively in use.
* Clear Chrome's Cache and Data: Go to Chrome's Settings > Privacy and security > Clear browsing data. Choose a time range and select "Cached images and files" and "Cookies and other site data."

3. Disable Extensions:

Temporarily Disable: Go to Chrome's Settings > More tools > Extensions and disable all extensions. If the error disappears, re-enable extensions one by one to identify the culprit.

4. Disable "Embedded IGV":

Emedgene interface: Go to any Emedgene case > Analysis tools > Varpage > Side bar > Applications > "Embedded IGV" and disable it.

5. Update Chrome:

Check for Updates: Ensure you're using the latest version of Chrome, as updates often contain bug fixes and memory optimizations.

6. Restart Chrome and Your Device:

* Close Chrome: Completely exit Chrome, including any background processes.
* Restart Your Device: Shut down your computer or phone and restart it. This clears temporary files and refreshes system resources.

7. Consider Hardware Issues:

If none of these solutions work, consider potential hardware issues, such as faulty RAM or disk problems. Consult a technician for further diagnosis.

Adapted from Google Chrome [help center](https://support.google.com/chrome/thread/252045457/chrome-shows-aw-snap-not-enough-memory-error-without-even-opening-any-tabs-or-other-applications?hl=en).


---

# 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://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/troubleshooting/performance_issue_troubleshooting.md?ask=<question>&goal=<user_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.