You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 13, 2020. It is now read-only.
Testing / evaluating parse using an Ubuntu Linux computer.
Parse UNIX library seems to be in a continuous loop eating 100% of CPU.
The problematic code seems to be in parse.c, function: int parseProcessNextPushNotification(ParseClient client), the following lines:
The while loop continues to run as the CURLcode result = curl_easy_recv returns CURLE_OK.
However the 'read' parameter passed to curl_easy_recv has a value of 0 after call that indicates a closed connection according to http://curl.haxx.se/libcurl/c/curl_easy_recv.html.
The result is 100% cpu utilization and inability to process subsequent push messages.
I think the correct form would be to use if ((result == CURLE_OK) && (read > 0))
The text was updated successfully, but these errors were encountered:
dfszb
changed the title
embedded library runs in a loop inside int parseProcessNextPushNotification(ParseClient client)
embedded library seems to have infinite loop inside parseProcessNextPushNotification function.
Jan 21, 2016
dfszb
changed the title
embedded library seems to have infinite loop inside parseProcessNextPushNotification function.
embedded library seems to run infinite loop inside parseProcessNextPushNotification function.
Jan 21, 2016
Testing / evaluating parse using an Ubuntu Linux computer.
Parse UNIX library seems to be in a continuous loop eating 100% of CPU.
The problematic code seems to be in parse.c, function: int parseProcessNextPushNotification(ParseClient client), the following lines:
The while loop continues to run as the CURLcode result = curl_easy_recv returns CURLE_OK.
However the 'read' parameter passed to curl_easy_recv has a value of 0 after call that indicates a closed connection according to http://curl.haxx.se/libcurl/c/curl_easy_recv.html.
The result is 100% cpu utilization and inability to process subsequent push messages.
I think the correct form would be to use if ((result == CURLE_OK) && (read > 0))
The text was updated successfully, but these errors were encountered: