SVN Bug Reports

[Jaedayr]

Are you using Snacko's script or Eclipse to get the latest revision? Because that seems to be where the problem lies.

I use Eclipse.

[slapshot5]

r10080

Over the last week or more, I've noticed my java Heap errors getting exponentially worse. It never used to be this bad. I don't know what changed. I always run from Eclipse and use LQ pics.

Code: Select all

Caused by: java.lang.OutOfMemoryError: Java heap space


-slapshot5

[Braids]

i am actively working on reducing forge's heap footprint, with more help in following commits. please hang in there!

[slapshot5]

i am actively working on reducing forge's heap footprint, with more help in following commits. please hang in there!

Looking forward to it. And, Welcome! BTW.

-slapshot5

[Chris H.]

r10080

Over the last week or more, I've noticed my java Heap errors getting exponentially worse. It never used to be this bad. I don't know what changed. I always run from Eclipse and use LQ pics.

Code: Select all

Caused by: java.lang.OutOfMemoryError: Java heap space


`
Strange, we have similar systems and I have not had any heap space errors since I figured out how to increase my heap space.

I have been playing a quest that I started a couple of weeks ago. I just finished a match using the mac version of the last beta.

[Jaedayr]

r10111

I do not understand all the meaning behind the messages below. I do understand that Forge is unplayable today for me. I clicked Continue Quest over five minutes ago, my CPU is sitting at 100pct with no quest window. From reading the start of the message I get the idea that this is not a fix to a problem, but perhaps a work in progress?

Code: Select all

Prepare for a significant delay. I was forced to load all cards into memory by the following chain of events (most recent first):
java.lang.Exception: not really an error; just note the stack trace
   at forge.card.cardFactory.CardFactory.getCards(CardFactory.java:128)
   at forge.quest.data.QuestUtil.setupQuest(QuestUtil.java:97)
   at forge.ReadQuest_Assignment.run(ReadQuest_Assignment.java:216)
   at forge.quest.gui.main.QuestQuest.readQuests(QuestQuest.java:71)
   at forge.quest.gui.main.QuestQuest.getQuests(QuestQuest.java:55)
   at forge.quest.gui.main.QuestMainPanel.createQuestPanel(QuestMainPanel.java:415)
   at forge.quest.gui.main.QuestMainPanel.refreshNextMatchPanel(QuestMainPanel.java:541)
   at forge.quest.gui.main.QuestMainPanel.refresh(QuestMainPanel.java:530)
   at forge.quest.gui.main.QuestMainPanel.initUI(QuestMainPanel.java:93)
   at forge.quest.gui.main.QuestMainPanel.<init>(QuestMainPanel.java:86)
   at forge.quest.gui.QuestFrame.<init>(QuestFrame.java:48)
   at forge.Gui_QuestOptions.continueQuestButton_actionPerformed(Gui_QuestOptions.java:228)
   at forge.Gui_QuestOptions$2.actionPerformed(Gui_QuestOptions.java:135)
   at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
   at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
   at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
   at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
   at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
   at java.awt.Component.processMouseEvent(Unknown Source)
   at javax.swing.JComponent.processMouseEvent(Unknown Source)
   at java.awt.Component.processEvent(Unknown Source)
   at java.awt.Container.processEvent(Unknown Source)
   at java.awt.Component.dispatchEventImpl(Unknown Source)
   at java.awt.Container.dispatchEventImpl(Unknown Source)
   at java.awt.Component.dispatchEvent(Unknown Source)
   at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
   at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
   at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
   at java.awt.Container.dispatchEventImpl(Unknown Source)
   at java.awt.Window.dispatchEventImpl(Unknown Source)
   at java.awt.Component.dispatchEvent(Unknown Source)
   at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
   at java.awt.EventQueue.access$000(Unknown Source)
   at java.awt.EventQueue$1.run(Unknown Source)
   at java.awt.EventQueue$1.run(Unknown Source)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
   at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
   at java.awt.EventQueue$2.run(Unknown Source)
   at java.awt.EventQueue$2.run(Unknown Source)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
   at java.awt.EventQueue.dispatchEvent(Unknown Source)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
   at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
   at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
   at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
   at java.awt.EventDispatchThread.run(Unknown Source)


[Braids]

r10095 defers a large portion of forge's startup delay to certain cases: the card shop, limited formats, generating random decks, and deck editing. the message you are getting indicates that the particular feature you are using is incurring forge's ordinary startup delay. in other words, i should add quest mode to that list.

the delay is significantly reduced when playing in constructed formats using specific or random (but not randomly generated) decks. r10095 also reduces forge's overall heap requirements by keeping fewer copies of the all the cards in memory.

are you able to run the latest beta? does it take over five minutes to show forge's first window?

would a progress bar with estimated time of completion help your experience?


edit 1: fixed rev numbers.

edit 2: the progress bar has taken a back seat to fixing whatever it is that i apparently broke with r10095.

[goonjamin]

I'd vote yes to a progress bar. As a new forge player there have been a few times I thought the program had frozen when it was actually still chuging along in the background.

[Jaedayr]

are you able to run the latest beta? does it take over five minutes to show forge's first window?

would a progress bar with estimated time of completion help your experience?

Yes I can run the latest beta, and I usually grab the latest rev every day so I can play and test the latest and greatest. Starting Forge usually takes less than a minute, and starting/continuing a quest usually takes about 10-15 seconds.

Today I saw that message twice, first (I think) when I tried to download LQ set pics. After about 45 seconds the download proceeded to successful completion (usually the download starts in about ten seconds). The second time I got it was as explained above, and I finally gave up waiting and decided to wait for more info, which you have provided.

I don't really need a progress bar, given a choice I would vote for instantaneous loading so there would never be the need for the bar.

[Braids]

@Jaedayr: well, that's valuable information. this wasn't supposed to make anything slower overall. slower in certain places, yes, but not overall. i get fail. working on it.

[Chris H.]

I don't really need a progress bar, given a choice I would vote for instantaneous loading so there would never be the need for the bar.

`
I actually like Rob's new progress bar. I would rather not have to wait, but if I do the progress bar can distract me for the several seconds that it is there. Helps to pass the time.

[Rob Cashwalker]

I had intended that the progress bar get more use.

Java has a built-in progress bar dialog, but in order to make use of their stuff, I'd have to rewrite a lot of stuff to run in a spawned thread. The progress bar I made can be used anywhere in our existing code.

[Jaedayr]

r10143

Thanks to the recent updates I am able to run Forge and play the quest as expected. So today I played a quest match and tried to go into the quest deck editor. I got an error with the cardname Vedalken AEthermage. Apparently I had quested with the new spelling and when the change was reverted in the cardfolder, it stayed in my saved quest info.

No problem, I will just start another quest... except that when I press the New Quest button nothing happens. It does not indicate that I pressed it, it refreshes immediately, my CPU shows 0 activity and memory usage stays constant. I tried this several times. I exited out of Forge, came back and tried to start a new quest and the same thing happened. When I clicked Continue Quest it continued as normal but I can't get into the deck editor.

Is there something I can delete/change in order to start a new quest, or is there a coding change needed somewhere?

[Sloth]

r10143
No problem, I will just start another quest... except that when I press the New Quest button nothing happens. It does not indicate that I pressed it, it refreshes immediately, my CPU shows 0 activity and memory usage stays constant. I tried this several times. I exited out of Forge, came back and tried to start a new quest and the same thing happened. When I clicked Continue Quest it continued as normal but I can't get into the deck editor.

Is there something I can delete/change in order to start a new quest, or is there a coding change needed somewhere?

I have the same problem Jaedayr. Must be a side effect of the big changes going on.

[Hellfish]

You can mail me the questData, if you've played it long, and I'll fix it.