XTension 9.4.46 crashing

[Andy Poggio]

James,

I’ll do as you suggest.  Meanwhile, I found this in the log today:

12/27/22 6:22:16 AM  Sending OFF for "Tony desk light"
12/27/22 6:22:26 AM  XTUnit.handleCommandFromXTension( command=OFF, error=name 'self' is not defined)
12/27/22 6:22:26 AM  Traceback (most recent call last):
12/27/22 6:22:26 AM    File "/Applications/XTension/XTension.app/Contents/Resources/Plugins/tplink.isf/tplink.py", line 2766, in getDevice
12/27/22 6:22:26 AM      newData = future.result( 10)
12/27/22 6:22:26 AM    File "concurrent/futures/_base.pyc", line 447, in result
12/27/22 6:22:26 AM  concurrent.futures._base.TimeoutError
12/27/22 6:22:26 AM  
12/27/22 6:22:26 AM  During handling of the above exception, another exception occurred:
12/27/22 6:22:26 AM  
12/27/22 6:22:26 AM  Traceback (most recent call last):
12/27/22 6:22:26 AM    File "/Applications/XTension/XTension.app/Contents/Resources/python3/Resources/xtension_plugin/xtension_plugin.py", line 3251, in handleCommandFromXTension
12/27/22 6:22:26 AM      handler( theCommand)
12/27/22 6:22:26 AM    File "/Applications/XTension/XTension.app/Contents/Resources/Plugins/tplink.isf/tplink.py", line 869, in xtTurnOff
12/27/22 6:22:26 AM      workDevice = self.getDevice(self.address, True) # pass true to do a rediscovery if the device was not found
12/27/22 6:22:26 AM    File "/Applications/XTension/XTension.app/Contents/Resources/Plugins/tplink.isf/tplink.py", line 225, in getDevice
12/27/22 6:22:26 AM      workDevice = getDevice( address, rediscover, ipaddress=self.lastKnownIP)
12/27/22 6:22:26 AM    File "/Applications/XTension/XTension.app/Contents/Resources/Plugins/tplink.isf/tplink.py", line 2769, in getDevice
12/27/22 6:22:26 AM      self.debugLog( f"timeout error in discover single with IP {singleIP}", xtLogRed)
12/27/22 6:22:26 AM  NameError: name 'self' is not defined

There was not obvious crash, but this can’t be good.

—andy


> On Dec 27, 2022, at 4:37 AM, James Sentman <james at sentman.com> wrote:
> 
> Frustratingly the crash report does not actually include anything that is helping me see whats going on. The last thing it’s doing prior to the crash is to pass control to Apple’s core foundation libs to run the next event loop and it’s crashing before those actually seem to do anything.
> 
> Do you have more windows open than usual? Are any of them a View that might have some controls embedded that are html rendered? I do see notes about other threads that are handling the javascript systems that are loaded for such a thing. They don’t immediately indicate any kind of problem but would be interesting to know if closing windows makes it go away.
> 
> The other and most classic possibility is a corrupted script somewhere, though the crash log is not obviously point to that it doesn’t mean that isn’t the problem.
> 
> I would restart XTension holding down the option key and from the startup options dialog select to log detailed startup information. Have a look through the very large amount of logged information for anything written in red or forward me a copy of the output off the list and I’ll have a look through for anything obvious as well. Then you can quit and restart normally. If anything is listed in red, or just as a matter of course the next thing I would do would be to use the Database menu to save off an archive of the database just in case and then restart again holding the option key and select “recompile all scripts” from the same dialog. This will cause you to lose any saved context in any script, the local variables that are otherwise consistent. Watch as it runs through that and be ready to answer any locate this app dialogs that might come up if it needs you to find the app that a script is targeting. 
> 
> Then let me know what happens.
>   James
> 
> 
> 
>> On Dec 26, 2022, at 12:53 PM, Andy Poggio <apoggio at pacbell.net> wrote:
>> 
>> Crashed Thread:        0  Dispatch queue: com.apple.main-thread
>> 
>> Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
>> Exception Codes:       0x0000000000000001, 0x0000000000000000
>> Exception Note:        EXC_CORPSE_NOTIFY
>> 
>> Termination Signal:    Illegal instruction: 4
>> Termination Reason:    Namespace SIGNAL, Code 0x4
>> Terminating Process:   exc handler [0]
>> 
>> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
>> 0   com.apple.CoreFoundation      	0x00007fff579b753c __CFRunLoopServiceMachPort + 652
>> 1   com.apple.CoreFoundation      	0x00007fff579b6757 __CFRunLoopRun + 1783
>> 2   com.apple.CoreFoundation      	0x00007fff579b5dd3 CFRunLoopRunSpecific + 483
>> 3   com.apple.HIToolbox           	0x00007fff56ca0d96 RunCurrentEventLoopInMode + 286
>> 4   com.apple.HIToolbox           	0x00007fff56ca0b06 ReceiveNextEventCommon + 613
> 
> Thanks,
>  James
> 
> 
> James Sentman                       http://www.PlanetaryGear.org		http://MacHomeAutomation.com
> 
> 
> 
> 
> _______________________________________________
> XTensionList mailing list
> XTensionList at machomeautomation.com
> http://mail.machomeautomation.com/mailman/listinfo/xtensionlist