"Improving Steam Client stability on Linux: setenv and multithreaded environments" - I wrote about fixes we've made in the most recent Steam client release on Linux: https://ttimo.typepad.com/blog/2024/11/the-steam-client-update-earlier-this-week-mentions-fixed-some-miscellaneous-common-crashes-in-the-linux-notes-which-i-wante.html #steam #linux #steamdeck
=> More informations about this toot | More toots from TTimo@mastodon.social
@TTimo i wonder for all the getenv stuff if we can just force it into the main thread, which should hopefully be safe? like override the getenv symbol and then call the original one with syscall interface in the main thread. not sure if it wouldnt be more pain or not.
=> More informations about this toot | More toots from darix@mastodon.social
@TTimo A fascinating little read!
=> More informations about this toot | More toots from glyph@mastodon.social
@TTimo Reminds me a discussion with PD a couple of weeks ago. "We have this crash in OpenSSL, we will have to work with them to determine the cause". Me: "You have a crash in getenv(). In a multi-threaded program. Leave the people from OpenSSL alone. Don't use setenv() in your code."
=> More informations about this toot | More toots from mavetju@aus.social
@TTimo Nice work!
=> More informations about this toot | More toots from JayT@fosstodon.org This content has been proxied by September (ba2dc).Proxy Information
text/gemini