{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreic2tb5grozdnyfshsjoamcz7fqnexaxs5mjek4fobssbqprbgswh4",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mklwm3zfpx42"
  },
  "path": "/viewtopic.php?t=33382&p=272948#p272948",
  "publishedAt": "2026-04-29T00:51:47.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "https://repo.palemoon.org/MoonchildProd ... ent_win.cc"
  ],
  "textContent": "That's interesting, it's hitting the Chromium IPC code:\n\nhttps://repo.palemoon.org/MoonchildProd ... ent_win.cc\n\nWe haven't touched that code since forking off from Firefox. I remember updating some of the locking code near here ages ago, apparently in Issue #2003... wonder if maybe something in there is getting a bit long in the tooth and holding us back from taking changes we should be able to take?\n\nStill kind of wondering why it's called here, though, I thought the Chromium IPC was used mostly for interprocess communication. So now I'm admittedly wondering if this is really called from JS directory, or if it's one of those tools I know is linked into Chromium IPC that gives us more info about how memory is used that's crashing out here? Like yeah, I know it got there... just wondering what called into it.\n\n* * *",
  "title": "Platform Development • Re: The browser hang with 0 CPU load.",
  "updatedAt": "2026-04-29T00:51:47.000Z"
}