Changes between Version 3 and Version 4 of Ticket #1361
- Timestamp:
- Apr 27, 2012, 11:21:29 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1361
- Property Summary Game hangs ~2s into custom-made map → Qbot hangs ~2s into custom-made map
-
Ticket #1361 – Description
v3 v4 1 While developing the wall placement system, I created the attached map to do some basic testing. At some point during approximately the last two weeks (call it roughly between [11494] and [11672]), something changed that caused the game to go into what looks like an infinite JS loop about 2 seconds into the map . This happens only when the window has focus but regardless of the user's activity, and I haven't seen this happen on other maps.1 While developing the wall placement system, I created the attached map to do some basic testing. At some point during approximately the last two weeks (call it roughly between [11494] and [11672]), something changed that caused the game to go into what looks like an infinite JS loop about 2 seconds into the map, when using Qbot as the AI. This happens only when the window has focus but regardless of the user's activity, and I haven't seen this happen on other maps, nor does it happen for other AIs like Jubot. 2 2 3 By "hangs", I mean becomes unresponsive and takes up 100% CPU, requiring to be killed from the process monitor. I've observed this happening for revision [11683], the most recent revision at the time of writing .3 By "hangs", I mean becomes unresponsive and takes up 100% CPU, requiring to be killed from the process monitor. I've observed this happening for revision [11683], the most recent revision at the time of writing, using Qbot. 4 4 5 5 Attaching !WinDbg in a debug build during the hang shows that it's hanging somewhere in !SpiderMonkey as a result of a call to `ScriptInterface::CallFunction_` while doing some AI work. … … 43 43 }}} 44 44 45 Seeming to indicate that perhaps some AI computation is going into a loop? 45 Indicating that some AI computation in qbot is going into a loop. 46 46 47 47 Attaching to a release build shows similar results: also in !SpiderMonkey, after a result to a script interface call with the `HandleMessage` function name.