EldoS | Feel safer!

Software components for data protection, secure storage and transfer

NullReferenceException at SBSocket.TElSocket.HandleRecvCompleted

Posted: 09/19/2014 06:18:37
by Maarten Merken (Basic support level)
Joined: 09/19/2014
Posts: 2


We are developing an WinRT, Windows Phone 8.1 app and are using the TElHTTPSClient for posting data to our backend via SecureBlackBox.

However, about 1 in 10 calls result in a NullReferenceException located at SBSocket.TElSocket.HandleRecvCompleted.

We started out using your Async libraries to use PostAsync on the TElHTTPSClient, however this resulted in 7 in 10 calls to execute badly and throwing the NullReferenceException.

So switching to the default synchronous implementation was an improvement, but still the problem persists.

Could you please look into this ? This is crucial for the performance and reliability of our app.

We'd also like to point out that the implementation of your Async libraries are useless in large sequential network calls.
Since these just wrap the sync calls in a Task.Factory.Run awaitable Task.
We strongly recommend you to refactor your Async libraries.


Posted: 09/22/2014 04:20:57
by Ken Ivanov (Team)

Hi Maarten,

Sorry for the delayed answer.

Could you please provide us with some details of the issue by answering the questions below:

1) On what stage of connection does the issue occur? In particular,

- do OnReceivingHeaders, OnDocumentBegin events fire;

- do you get any data in the output stream at the moment when the exception is thrown?

2) Do you send HTTP or HTTPS requests?

3) What kind of data are you submitting (type and length)?

4) Did you notice anything particular about the failing requests (data lengths perhaps) or they are fairly random?

Could you please also specify the build number and the version of the product you are using?

Thanks in advance,

Posted: 09/29/2014 03:33:20
by Maarten Merken (Basic support level)
Joined: 09/19/2014
Posts: 2

Dear Ken,

Below our answers :

1) This happens after all data is successfully received, the method that throws the exception is HandleRecvCompleted.


3) We are submitting JSON data in variable lengths

4) It appears to be random, sometimes the first request that fails, sometimes another request later in the lifecycle of the application. We estimate the issue to happen 1 in 10 calls.

We are using the WinStore 8.1 libraries version 12.0.259.

The problem seemed to be worse when we used the WinRT variant of the libraries.

The data is received, but sometimes after receiving the data, we get this exception.

Thanks for investigating.


Posted: 09/30/2014 08:57:55
by Ken Ivanov (Team)

Hi Maarten,

I believe we've managed to localize the NullReferenceException issue and are working on a solution at the moment. The patch will go to the next SecureBlackbox product update, which is going to be released within three weeks.

Thanks and kind regards,




Topic viewed 658 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS business operates as a division of /n software, inc. For more information, please read the announcement.

Got it!