memory requirement of webbrowser is very high on heavy deck usage
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Describe the bug
Deck is using a lot of RAM on the client for the webbrowser on heavy deck usage - On Windows Firefox can consume 5-6 GB for around 20 decks with 200 cards each. Edge is a bit better (2-3 GB), but this is a lot for such a simple interface I think. Webbrowser can become unresponsive in this situations. The server side is not the problem. System load is below 1.00 and cpu and memory usage are normal.
To Reproduce
Steps to reproduce the behavior:
- Create a few decks
- Create a lot of cards in each deck / list
- Look to the memory consumption of the web browser
Expected behavior
Memory consumption of webbrowser should not be not so excessive that the browser stops to react.
Client details:
- OS: Windows 10
- Browser Firefox 102.4.0esr, Edge 108.8.1462.42
- Device: Desktop
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the problem by creating multiple decks with many cards, then observe browser memory use in Firefox and Edge on Windows. Start with client-side profiling while increasing deck and card counts; done means memory use is substantially reduced and the browser remains responsive under heavy deck usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100