Don't clean up LLVM state when exiting in a bad way - Mailing list pgsql-hackers

From Jelte Fennema
Subject Don't clean up LLVM state when exiting in a bad way
Date
Msg-id AM5PR83MB0178C52CCA0A8DEA0207DC14F7FF9@AM5PR83MB0178.EURPRD83.prod.outlook.com
Whole thread Raw
Responses Re: Don't clean up LLVM state when exiting in a bad way
Re: Don't clean up LLVM state when exiting in a bad way
Re: Don't clean up LLVM state when exiting in a bad way
List pgsql-hackers
Hi,

I ran into some segfaults when using Postgres that was compiled with LLVM 7. According to the backtraces these crashes happened during the call to llvm_shutdown, during cleanup after another out of memory condition. It seems that calls to LLVMOrcDisposeInstance, can crash (at least on LLVM 7) when LLVM is left in bad state. I attached the relevant part of the stacktrace to this email.

With the attached patch these segfaults went away. The patch turns llvm_shutdown into a no-op whenever the backend is exiting with an error. Based on my understanding of the code this should be totally fine. No memory should be leaked, since all memory will be cleaned up anyway once the backend exits shortly after. The only reason this cleanup code even seems to exist at all is to get useful LLVM profiling data. To me it seems be acceptable if the profiling data is incorrect/missing when the backend exits with an error.  

Jelte
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: NAMEDATALEN increase because of non-latin languages
Next
From: Zhihong Yu
Date:
Subject: Re: Don't clean up LLVM state when exiting in a bad way