Talk:Library Initialization - Revision history

Matt at 07:59, 30 July 2019

2019-07-30T07:59:49Z

Jwalton at 20:59, 29 July 2019

2019-07-29T20:59:37Z

Jwalton at 20:59, 29 July 2019

2019-07-29T20:59:01Z

Jwalton at 20:58, 29 July 2019

2019-07-29T20:58:38Z

Matt: Raise CRYPTO_cleanup_ex_data() issue

2015-05-07T14:30:40Z

Raise CRYPTO_cleanup_ex_data() issue

New page

You said:
"CRYPTO_cleanup_all_ex_data and ERR_remove_state should be called on each thread, and not just the main thread."

However the FAQ says:

"Brutal" (thread-unsafe) Application-global cleanup functions:

ERR_free_strings(), EVP_cleanup() and CRYPTO_cleanup_all_ex_data().'

And the code comments for CRYPTO_cleanup_all_ex_data() say:
/* Release all "ex_data" state to prevent memory leaks. This can't be made
* thread-safe without overhauling a lot of stuff, and shouldn't really be
* called under potential race-conditions anyway (it's for program shutdown
* after all). */

So I don't think its right to say CRYPTO_cleanup_all_ex_data() should be called on each thread.
--[[User:Matt|Matt]] ([[User talk:Matt|talk]]) 14:30, 7 May 2015 (UTC)

← Older revision		Revision as of 07:59, 30 July 2019
Line 20:		Line 20:
	: This is going back 5 or 7 years... I was having trouble under Valgrind. I asked a few messages on the mailing list about how to cleanup properly. Both CRYPTO_cleanup_all_ex_data and ERR_remove_state (on each thread) dropped out of the messages/questions. Also see [http://openssl.6102.n7.nabble.com/Order-of-Cleanup-to-avoid-memory-leaks-td48474.html Order of Cleanup to avoid memory leaks?]. I don't know if it correct thing to do nowadays.		: This is going back 5 or 7 years... I was having trouble under Valgrind. I asked a few messages on the mailing list about how to cleanup properly. Both CRYPTO_cleanup_all_ex_data and ERR_remove_state (on each thread) dropped out of the messages/questions. Also see [http://openssl.6102.n7.nabble.com/Order-of-Cleanup-to-avoid-memory-leaks-td48474.html Order of Cleanup to avoid memory leaks?]. I don't know if it correct thing to do nowadays.
	: [[User:Jwalton\|Jwalton]] ([[User talk:Jwalton\|talk]]) 20:58, 29 July 2019 (UTC)		: [[User:Jwalton\|Jwalton]] ([[User talk:Jwalton\|talk]]) 20:58, 29 July 2019 (UTC)
		+
		+	: In many cases it is not necessary to do anything to clean up each individual threads (from OpenSSL 1.1.0+). As long as the thread exits before OpenSSL does then it should get cleaned up automatically. There
		+	are some caveats on that (especially for windows). You can force OpenSSL to cleanup a thread using OPENSSL_thread_stop(). See the man page for that function to see a discussion on the caveats (in particular see the "Notes" section).
		+
		+	: --[[User:Matt\|Matt]] ([[User talk:Matt\|talk]]) 07:59, 30 July 2019 (UTC)

@@ Line 18: / Line 18: @@
 --[[User:Matt|Matt]] ([[User talk:Matt|talk]]) 14:30, 7 May 2015 (UTC)
-: This is going back 5 or 7 years... I was having trouble under Valgrind. I asked a few messages on the mailing list about how to cleanup properly. Both CRYPTO_cleanup_all_ex_data and ERR_remove_state (on each thread) dropped out of it. Also see [http://openssl.6102.n7.nabble.com/Order-of-Cleanup-to-avoid-memory-leaks-td48474.html Order of Cleanup to avoid memory leaks?]. I don't know if it correct thing to do nowadays.
+: This is going back 5 or 7 years... I was having trouble under Valgrind. I asked a few messages on the mailing list about how to cleanup properly. Both CRYPTO_cleanup_all_ex_data and ERR_remove_state (on each thread) dropped out of the messages/questions. Also see [http://openssl.6102.n7.nabble.com/Order-of-Cleanup-to-avoid-memory-leaks-td48474.html Order of Cleanup to avoid memory leaks?]. I don't know if it correct thing to do nowadays.
 : [[User:Jwalton|Jwalton]] ([[User talk:Jwalton|talk]]) 20:58, 29 July 2019 (UTC)

@@ Line 18: / Line 18: @@
 --[[User:Matt|Matt]] ([[User talk:Matt|talk]]) 14:30, 7 May 2015 (UTC)
-: This is going back 5 or 7 years... I was having trouble under Valgrind. I asked a few messages on the mailing list about how to cleanup properly. Both CRYPTO_cleanup_all_ex_data and ERR_remove_state (on each thread) dropped out of it. Also see [http://openssl.6102.n7.nabble.com/Order-of-Cleanup-to-avoid-memory-leaks-td48474.html Order of Cleanup to avoid memory leaks?].
+: This is going back 5 or 7 years... I was having trouble under Valgrind. I asked a few messages on the mailing list about how to cleanup properly. Both CRYPTO_cleanup_all_ex_data and ERR_remove_state (on each thread) dropped out of it. Also see [http://openssl.6102.n7.nabble.com/Order-of-Cleanup-to-avoid-memory-leaks-td48474.html Order of Cleanup to avoid memory leaks?]. I don't know if it correct thing to do nowadays.
 : [[User:Jwalton|Jwalton]] ([[User talk:Jwalton|talk]]) 20:58, 29 July 2019 (UTC)

← Older revision		Revision as of 20:58, 29 July 2019
Line 17:		Line 17:
	So I don't think its right to say CRYPTO_cleanup_all_ex_data() should be called on each thread.		So I don't think its right to say CRYPTO_cleanup_all_ex_data() should be called on each thread.
	--[[User:Matt\|Matt]] ([[User talk:Matt\|talk]]) 14:30, 7 May 2015 (UTC)		--[[User:Matt\|Matt]] ([[User talk:Matt\|talk]]) 14:30, 7 May 2015 (UTC)
		+
		+	: This is going back 5 or 7 years... I was having trouble under Valgrind. I asked a few messages on the mailing list about how to cleanup properly. Both CRYPTO_cleanup_all_ex_data and ERR_remove_state (on each thread) dropped out of it. Also see [http://openssl.6102.n7.nabble.com/Order-of-Cleanup-to-avoid-memory-leaks-td48474.html Order of Cleanup to avoid memory leaks?].
		+	:
		+	: I don't know if it correct thing to do nowadays.
		+	:
		+	: [[User:Jwalton\|Jwalton]] ([[User talk:Jwalton\|talk]]) 20:58, 29 July 2019 (UTC)