CLIENT - unhandled error in GUI - OutOfMemoryError
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 940
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 160
Description
Error type: CLIENT - unhandled error in GUI - OutOfMemoryError
Client version: 1.4.56-V3 (build: 2025-02-09 16:02)
Java version: 1.8.0_201
Default charset: UTF-8
GC overhead limit exceeded
Stack trace:
mage.constants.SubType.values(SubType.java:10)
mage.constants.SubType.fromString(SubType.java:629)
mage.cards.repository.CardInfo.getSubTypes(CardInfo.java:372)
mage.cards.mock.MockCard.(MockCard.java:52)
mage.cards.repository.CardInfo.createMockCard(CardInfo.java:258)
mage.client.deckeditor.CardSelector.filterCards(CardSelector.java:481)
mage.client.deckeditor.CardSelector.loadCards(CardSelector.java:229)
mage.client.deckeditor.DeckEditorPanel.showDeckEditor(DeckEditorPanel.java:262)
mage.client.deckeditor.DeckEditorPane.show(DeckEditorPane.java:53)
mage.client.MageFrame.showDeckEditor(MageFrame.java:1428)
and other 22 lines
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure when opening the deck editor, then trace the reported path from MageFrame.showDeckEditor through CardSelector.loadCards and filterCards. Inspect SubType.values/fromString, CardInfo.getSubTypes, and MockCard construction in the named Java files. Done means the reported GUI workflow no longer reaches the OutOfMemoryError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100