Improper use of Task .Result when making async methods sync about .net-sdk

[endret]

hi @magkal ,
Thank you the report. We're starting to investigate of your issue.

Regards,
Endre

[endret]

Hi @magkal,

I think we should split this issue into two parts:

1. Thread synchronization deadlock
   Have got ever any deadlock when using ConfigCat client?
2. Thread pool issue (i guess you had thread pool starvation)
   Can you explain what does it mean 'too often'? Why are you using in this case synchronous method instead of async?
   Is it possible to insert a copy of some lines of code about configcat usage?

I create some changes to replace an elegant .Result / .Wait but it won't solve your ThreadPool issues. (#18)

Thanks,
Endre

[magkal]

Hi thanks for the update,
You're right it's two separate issues.

1. We were unable to get our azure webapp starting after deploy and did some debugging with dnSpy, which always got stuck on the configcat library causing a deadlock. As soon as we refactored the code calling Sync methods in configcat, to properly await the result, our azure webapp started and was healthy.

2. Regarding the thread pooling is likely something else that we mixed up in this. Since we upgraded multiple packages within the same test release we did, and an issue we ran into seemed to be caused by thread pool starvation. I think it's safe to disregard that within this github issue.

/Magnus

[endret]

Hi @magkal,

The new version was released.

If you have some time, can you try the async version of the methods?

Thanks,
Endre