Deck crashes or times out - when no of cards is high
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
the browser goes OOM due to high number of Upcoming cards for a user
To Reproduce
Steps to reproduce the behavior:
- Go to 'Deck'
- It will not complete the loading when the count of cards to be rendered is high, in my case it shows 4107
Expected behavior
it will try to load and keep on processing and ask for wait some times or will fail with OOM
Client details:
- OS: windows 10
- Browser Brave
suggested if count is more than 200, simple list is shared with links to cards which get loaded as modal on click and the board switch in background DOES NOT take place, we remain at this overview only
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
Start by reproducing the Deck loading path with a user who has more than 4,107 Upcoming cards, using the reported Windows 10 and Brave setup. Trace where the cards are rendered and how board switching occurs. Done means high card counts no longer exhaust the browser, while users receive a usable list with links that open cards as modals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100