-
Notifications
You must be signed in to change notification settings - Fork 260
"Out-of-memory in library OS" when creating and destroying a lot of threads #969
Comments
Thanks for including the repro code! Unfortunately I'm not surprised by the outcome, our codebase is plagued by memory leaks. |
Same thing happens when I remove fprintf and fflush. |
#1030 in Pal/Linux case: In Pal/Linux-SGX case, I'm not sure. |
With #1199, I was able to surpass >30,000 threads under Graphene-SGX and then I got bored and killed the process. This PR removes the But I still observe leaks of some other objects. Maybe it's PAL_HANDLEs? I didn't look into PAL logic. |
On the current master I'm hitting OOM (256MB enclave) ater ~5800 threads (with the exact same code as above). When I add a |
I'm using Graphene SGX latest code on main branch. I ran a C program that simply creates a thread, destroy it, then going on to create another one. After such loop is repeated 6445 times, the process dies with "Out-of-memory in library OS"
The C program I use is:
The inline debug log is attached.
log.txt
The text was updated successfully, but these errors were encountered: