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
We have shown that when we stress the APIs deployed in Posit Connect, in times of stress some processes generate the following error in some of the processes that Posit Connect launches to handle traffic.
If the content delivered by the api is in json format, the error is the following:
@apalacio9502 Will be probably be impossible to debug without access to the whole API code or reproducible example. Lots of situations can cause segfault, like adding a column to a data.table that does not have enough allocatable columns.
Hello,
We have shown that when we stress the APIs deployed in Posit Connect, in times of stress some processes generate the following error in some of the processes that Posit Connect launches to handle traffic.
If the content delivered by the api is in json format, the error is the following:
2023/10/13` 2:30:27 PM: Running swagger Docs at http://127.0.0.1:44785/__docs__/ 2023/10/13 2:37:17 PM: 2023/10/13 2:37:17 PM: *** caught segfault *** 2023/10/13 2:37:17 PM: address (nil), cause 'unknown'
If the content delivered by the api is in csv format, the error is the following:
2023/10/13 2:15:51 PM: Running swagger Docs at http://127.0.0.1:38325/__docs__/2023/10/13 2:16:25 PM:2023/10/13 2:16:25 PM: *** caught segfault ***2023/10/13 2:16:25 PM: address 0x10, cause 'memory not mapped'
Below I attach the Rsnapshot of when the api was deployed
I don't know how to make a reproducible example of this error.
Regards,
The text was updated successfully, but these errors were encountered: