HTTPSocket Error

Targets macOS
1

I’m getting a couple of reports from customers which look like below. I use the new xojo.core.httpsocket in various places within the application, and would like any pointers as to where this might be occurring from.

[quote]RaiseNilObjectException
Delegate.IM_Invoke%%osi4os
AddHandler.Stub.10%%si4os
HTTPSocket._ProcessPage%%o
HTTPSocket._ProcessData%%os
HTTPSocket._HandleNewData%%o
HTTPSocket.Event_DataAvailable%%o
XojoFramework$3146
XojoFramework$3082
XojoFramework$3121
XojoFramework$10824
XojoFramework$3774
XojoFramework$4466
CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION
__CFRunLoopDoTimer
__CFRunLoopDoTimers
__CFRunLoopRun
CFRunLoopRunSpecific
CFRunLoopRunInMode
RunCurrentEventLoopInMode
ReceiveNextEventCommon
_BlockUntilNextEventMatchingListInModeWithFilter
_DPSNextEvent
-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
-[NSApplication(NSEvent) nextEventMatchingMask:untilDate:inMode:dequeue:]
XojoFramework$1294
XojoFramework$1295
Delegate.Invoke%%
Application._CallFunctionWithExceptionHandling%%op
XojoFramework$9814
XojoFramework$1294
-[NSApplication run]
XojoFramework$9816
RuntimeRun
REALbasic._RuntimeRun
_Main
main
start[/quote]

2

Got an async request that gets returned AFTER a windows etc has closed (meaning the event handler is gone but the socket is still active) ?
With an event handler added via addhandler perhaps ?

it sure looks like a socket returning data or trying to return data to an event handler thats gone

3

Thanks Norman,
I’ll have to go through one by one. AFAICR; am not using AddHandler on any of the sockets. They’re either the base of a custom class (which is attached to itself to keep it in scope) or attached directly to a window, Seems like it’s one of the sockets on a window, just wish the stack would give me some clues. I’ve requested additional information from the customers.

This is the first time I’ve used the xojo.core.httpSocket instead of the regular httpSocket, so I’m a little anxious…

4

FWIW, InternetHeaders is a type available with the Classic sockets, so I’m betting your issue is not with the new ones.

5

Thanks Greg, this might be the clue I needed!