wakka9ca wrote:. . . However, it doesn't explain why
Glimpse the Unthinkable sometimes doesn't work - and the graveyard doesn't get shuffled back into the library either. That's the more puzzling point...

i'm not really qualified to help, sorry. if you have a reproducible {even intermittently} description, i would suggest you
file a formal bug report with Mantis.
wakka9ca wrote:Other than this, do you know if there is a known memory leak issue with the current version of Forge? The memory usage of java grows well beyond 1GB as the program runs (and keeps growing). I know Java has memory management but if you are using any external library written in other languages (like C), memory leak can still happen very subtlety. Is this normal? Also, I was wondering if a more efficient algorithm doesn't exist to load the card shop or the deck editor in quest mode when your collection has grown a bit larger. The load time can take up to 10 minutes.
i wouldn't say it's normal, but
we do know about it. i put a
serious dent in Forge's memory usage in version 1.1.0, released on 15 July this year. we still have more memory leaks, but they are becoming increasingly difficult to fix. i am unaware of any linkages with lower level libraries. we use a
lot of temporary card lists. the only explanation i can come up with is that we have circular references.
10 minutes? wow. there are plans to consolidate the deck editors, and we will be using memory efficient techniques called generators.
unofficially, i would recommend closing the program completely after two matches.
wakka9ca wrote:My PC is not the fastest computer out there but I can run MATLAB simulations on it no problem.
i usually have a machine with around 2GB of RAM and less than a 2 GHz processor, and it doesn't seem too bad. the deck editor takes a while, but usually much less than 10 minutes.
sorry i'm not much direct help.