Changes between Version 4 and Version 5 of Ticket #1361


Ignore:
Timestamp:
Apr 27, 2012, 11:22:28 PM (12 years ago)
Author:
vts
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1361 – Description

    v4 v5  
    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.
     1While 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.
    22
    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.
     3By "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.
    44
    55Attaching !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.