Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Game crashes after frivolous use of the Stack #440

Open
GoogleCodeExporter opened this issue Feb 2, 2016 · 10 comments
Open

Game crashes after frivolous use of the Stack #440

GoogleCodeExporter opened this issue Feb 2, 2016 · 10 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Play any card with an ability that costs only mana (ex. Honor Guard)
2. Put enough mana into your pool for at least two castings of the spell
3. Use the creature's ability once, interrupt it, and use its ability again.

What is the expected output? What do you see instead?
Expected: First casting of the ability resolves, then the second casting 
resolves.
Actual: First casting resolves, game freezes.

What version of the product are you using? On what operating system?
It has failed with out-of-the-box WTH0121.exe and the 1.21 EBOOT.PBP running 
under HBL 94r

Please provide any additional information below.
Not exactly a game-breaking bug, since I can just avoid using the stack, but it 
is a bug and so it belongs here in the issues section...

Original issue reported on code.google.com by tvil...@gmail.com on 21 Jul 2010 at 8:33

@GoogleCodeExporter
Copy link
Author

reproduced and verified, this issue also exist with multiple triggered may 
effect and the ai, 

both triggers enter the stack, first one goes to resolve, Ai is 
thinking.....2nd goes resolves while ai is thinking....crash.

Original comment by omegabla...@gmail.com on 3 Oct 2010 at 3:59

@GoogleCodeExporter
Copy link
Author

This also happens if you press X multiple times during an interrupt.  It did 
not do this with 0.12.1 with me, but has done it recently with 0.13.0.

Original comment by TranceW...@gmail.com on 4 Oct 2010 at 2:04

Attachments:

@GoogleCodeExporter
Copy link
Author

Original comment by omegabla...@gmail.com on 5 Oct 2010 at 1:35

  • Changed state: Verified
  • Added labels: Priority-High
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

opps changing to varified removes it from the list of issue(?why?)

Original comment by omegabla...@gmail.com on 5 Oct 2010 at 1:37

  • Changed state: New

@GoogleCodeExporter
Copy link
Author

verified means "it is fixed and I verified the fix".
If you confirmed that the issue exists, put it in the "accepted" status

Original comment by wagic.the.homebrew@gmail.com on 5 Oct 2010 at 1:42

@GoogleCodeExporter
Copy link
Author

void ActionLayer::setCurrentWaitingAction(ActionElement * ae){
  assert(!ae || !currentWaitingAction);
  currentWaitingAction = ae;
  if (!ae) cantCancel = 0;
}


windows points here with this error.

this issue happens intermintently so it is VERY tough to reproduce. 

Original comment by omegabla...@gmail.com on 5 Oct 2010 at 1:42

@GoogleCodeExporter
Copy link
Author

I have experienced this again.  I can now say however that it blue-screens on 
PSP-2Ks.  It freezes the PSP-1Ks with no blue screen.

Original comment by TranceW...@gmail.com on 12 Oct 2010 at 5:09

@GoogleCodeExporter
Copy link
Author

Happens to Pestilence too.

Original comment by saulot1...@gmail.com on 7 Nov 2010 at 7:25

Attachments:

@GoogleCodeExporter
Copy link
Author

just varifying this crash still exist.

Original comment by omegabla...@gmail.com on 20 Nov 2010 at 1:17

@GoogleCodeExporter
Copy link
Author

I haven't seen this bug since I updated to SVN.  Fixed?

Original comment by tvil...@gmail.com on 24 Mar 2011 at 9:24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant