📅 Original date posted:2011-08-11
🗒️ Summary of this message: Upgrade alerts needed as more 0.3.23 nodes are listening than 0.3.24. Chronic problem with new code causing CRITICAL_SECTION deadlocks. ThreadSanitizer may help.
📝 Original message:> they don't look good (I show about 3x as many 0.3.23 nodes listening as
> 0.3.24
*cough* Upgrade alerts.
> Very much needed, didn't TD say something about a friend who wanted to
> do research in this area?
I don't know if he'll actually do anything. Best assume this
"position" is still open.
>> 2. We've got a chronic problem with new code causing CRITICAL_SECTION
>> deadlocks
I've seen locks that track ordering relative to other locks and assert
when they are locked out of order.
Though it's not inversion related, running ThreadSanitizer might help
find other thread safety issues:
http://code.google.com/p/data-race-test/wiki/ThreadSanitizer
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 02:15:16
in reply to nevent1q…6hc0
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 02:15:16Event JSON
{
"id": "eb0cb3e541fb2eb8cf23666cd4029ea4e0d44623cc4b86d10027f452cd4d8c0a",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686104116,
"kind": 1,
"tags": [
[
"e",
"da86a222bb9948e30689d3ae99b8fbf27c245a1ccde301097e2d4ad972e99e61",
"",
"root"
],
[
"e",
"27dbcc9164b7a2d1daa483cedc5c077c08b341848626d963c6d3b349bcb16a20",
"",
"reply"
],
[
"p",
"5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6"
]
],
"content": "📅 Original date posted:2011-08-11\n🗒️ Summary of this message: Upgrade alerts needed as more 0.3.23 nodes are listening than 0.3.24. Chronic problem with new code causing CRITICAL_SECTION deadlocks. ThreadSanitizer may help.\n📝 Original message:\u003e they don't look good (I show about 3x as many 0.3.23 nodes listening as\n\u003e 0.3.24\n\n*cough* Upgrade alerts.\n\n\u003e Very much needed, didn't TD say something about a friend who wanted to\n\u003e do research in this area?\n\nI don't know if he'll actually do anything. Best assume this\n\"position\" is still open.\n\n\u003e\u003e 2. We've got a chronic problem with new code causing CRITICAL_SECTION\n\u003e\u003e deadlocks\n\nI've seen locks that track ordering relative to other locks and assert\nwhen they are locked out of order.\n\nThough it's not inversion related, running ThreadSanitizer might help\nfind other thread safety issues:\n\nhttp://code.google.com/p/data-race-test/wiki/ThreadSanitizer",
"sig": "b4274f3a129a6adb7b13f6e3b177eff85f3385f30a2447351b9aa3003526ae822b59345cd1bbf55a55e8264b463a0daa2dfa92d1f7d4f784ed4a9bee8c6458cd"
}