pold500 / gens-rerecording

Automatically exported from code.google.com/p/gens-rerecording
0 stars 0 forks source link

Lua scripts that run intensely for a long time freeze gens #47

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Write any code with a ton of gens.emulateframeinvisible()
2. Let the code run, and say 'No' to stopping code. 
3. Minimize Gens
4. Restore Gens
5. CRASH 

What is the expected output? 
The actual game window. 

What do you see instead?
A white screen. Inability to do anything but shut gens down via windows
task manager.

Original issue reported on code.google.com by kylethom...@gmail.com on 14 Dec 2008 at 5:56

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Wait, does it crash or does it freeze? What you described in the "what do you 
see
instead" section seems like a freeze, which is the intended behavior if you 
make an
infinite loop with no frame advance or wait calls in it and then specifically 
tell
Gens to ignore the safeguards and run forever. It might help to see the script 
you
are trying to run, because when I tried to reproduce this, I was unable to 
perform
step 3 (Gens wouldn't minimize).

Original comment by nitsuja-@hotmail.com on 14 Dec 2008 at 11:29

GoogleCodeExporter commented 8 years ago
I think the other emulators require you to kill them from the task manager too. 
But I
could probably force it to call wait() internally every once in a while, which 
would
be enough to let the script window's Stop button continue working in 
infinite-loop
situations... does that seem like a good idea to anyone else?

Original comment by nitsuja-@hotmail.com on 14 Dec 2008 at 11:57

GoogleCodeExporter commented 8 years ago
Yeah, that seems like a good safety precaution. But also, in regards to your
confusion about the issue, from the description on IRC I got the impression 
that the
behavior was different before getting the "should I kill your script?" message 
box
than after hitting "no".

Original comment by Upth...@gmail.com on 15 Dec 2008 at 4:03

GoogleCodeExporter commented 8 years ago
I think the CRASH part of this bug might be fixed in revision 189.

Original comment by nitsuja-@hotmail.com on 31 Dec 2008 at 1:37

GoogleCodeExporter commented 8 years ago
Probably fixed.

Original comment by nitsuja-@hotmail.com on 13 Jan 2009 at 6:53