Haven't been able to reproduce this yet, it was during a search to a resource, based on the screenie a hierarchical search, so it was probably RUNTIME_CHECK(wpPath.size() > 1); I think. If you get anything like this again (SIGABRT) check the shell console, it should state the file and line number of the failed assert().
Might have to go to extreme lengths to try and catch this one... the 'world' will be in a stable state, so if the condition I think is failing is failing (very intermittently...), we'll save the world (this will need a little extra work, as it will be a save from mid-frame), and hopefully the reconstructed world will do the same thing over and over again...
Hopefully none of the command updates change too much in the units they're updating before the path request, but that seems a reasonable assumption...