CTD in ECM Blastentity

[Eric Walch]

Oolite just crashed to desktop with the following backtrace:

Code: Select all

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib               	0x00007fff80756f10 objc_msgSend + 44
1   org.aegidian.oolite           	0x000000010029d262 -[OOECMBlastEntity update:] + 130 (OOECMBlastEntity.m:73)
2   org.aegidian.oolite           	0x0000000100077c34 -[Universe update:] + 4244 (Universe.m:5159)
3   org.aegidian.oolite           	0x000000010001e845 -[GameController doPerformGameTick] + 325 (GameController.m:344)
4   org.aegidian.oolite           	0x000000010001e6f9 -[GameController performGameTick:] + 105 (GameController.m:314)
5   com.apple.Foundation          	0x00007fff82fb4bc5 __NSFireTimer + 114
6   com.apple.CoreFoundation      	0x00007fff835babb8 __CFRunLoopRun + 6488
7   com.apple.CoreFoundation      	0x00007fff835b8d8f CFRunLoopRunSpecific + 575
8   com.apple.HIToolbox           	0x00007fff88ffc7ee RunCurrentEventLoopInMode + 333
9   com.apple.HIToolbox           	0x00007fff88ffc5f3 ReceiveNextEventCommon + 310
10  com.apple.HIToolbox           	0x00007fff88ffc4ac BlockUntilNextEventMatchingListInMode + 59
11  com.apple.AppKit              	0x00007fff80885eb2 _DPSNextEvent + 708
12  com.apple.AppKit              	0x00007fff80885801 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
13  com.apple.AppKit              	0x00007fff8084b68f -[NSApplication run] + 395
14  com.apple.AppKit              	0x00007fff808443b0 NSApplicationMain + 364
15  org.aegidian.oolite           	0x0000000100009ca7 main + 39 (main.m:13)
16  org.aegidian.oolite           	0x0000000100009190 start + 52

I noticed that last week a 'whom' parameter was added in trunk to the 'shipHitByECM' event. Could this be related?

I was docked for a long time in a random hits station at that time, with Oolite in the background doing some other computer stuff. The last errors in the normal log were:

Code: Select all

[script.javaScript.timeLimit]: ***** ERROR: Script "oolite-random-hits-hunter" ran for 0.366277 seconds and has been terminated.
[script.javaScript.stackTrace]:  0 (oolite-random-hits-hunter.js:176) <not a function frame>
[script.javaScript.stackTrace]:     this: [Script "oolite-random-hits-hunter" version (null)]
[script.javaScript.stackTrace]:     getExitCoordinates: function
[script.javaScript.stackTrace]:     getPatrolCoordinates: function
[script.javaScript.stackTrace]:     doScan: function
[script.javaScript.stackTrace]:     shipWillEnterWormhole: function
[script.javaScript.stackTrace]:     shipDied: function
[script.javaScript.stackTrace]:     shipBeingAttacked: function
[script.javaScript.stackTrace]:     shipSpawned: function
[script.javaScript.stackTrace]:     version: "2.1"
[script.javaScript.stackTrace]:     description: "Gives the Bounty Hunter NPCs from the Space Bars an individual name and rank on the ID computer and sets them to the right AI. Also causes hunters to regard hits from the spacebar\'s turret gunners or ..."
[script.javaScript.stackTrace]:     copyright: "November 2008 - But do what you like with it in your OXPs!"
[script.javaScript.stackTrace]:     author: "LittleBear, Eric Walch & Thargoid"
[script.javaScript.stackTrace]:     name: "oolite-random-hits-hunter"
[script.javaScript.stackTrace]:     ship: [Ship "Unidentified Commander" position: (0, 0, 0) scanClass: CLASS_NOT_SET status: STATUS_IN_FLIGHT] [read-only]
[script.javaScript.load.failed]: ***** Error loading JavaScript script /Users/ericwalch/Library/Application Support/Oolite/AddOns/RandomHits1.4.12.oxp/Scripts/oolite-random-hits-hunter.js -- could not run script
 

but that could be fully unrelated.

[Kaks]

Well, the ECMBlast error is precisely where it tried to shut itself off if the ship sending the countermeasure died in mid-sending. I thought I'd tested it, but that doesn't seem at all to be the case.

There's a fix for that, and it should be in trunk now: rev4812.


About the js errors, no idea, but it could be that they both originate from the same skirmish somewhere in the system you were staying at...