{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreid33fkpix33ayos354lp3zhybyyf6dgk5zxwp77z7gehkpscvhqdm",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mnwm6ab3a5f2"
  },
  "path": "/viewtopic.php?t=33144&p=275454#p275454",
  "publishedAt": "2026-06-10T10:03:13.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "already posted",
    "ELFIO"
  ],
  "textContent": "> For those still experiencing crashes, can you post a stacktrace?\n\nThat won't help (no symbol in binary). It just crashes somewhere in libxul.so.\n\nHowever, I already posted the messages PM spits out in the console (when started from it) when crashing: there's apparently a NaN happening and that could be the root cause of the issue.\n\nAs for the Inspector issue, PM does not crash per se (it just freezes), and here again, even running PM under gdb and interrupting it when it freeze, I'd just get a bunch of hexadecimal addresses without any function name in the backtrace. Also, the Inspector issue happens as well with PM 34.2\n\nTo get useful stack traces under Linux with a release build (i.e. a binary without debug symbols), you'd need to implement an exception handler using ELFIO to decode the addresses on the stack and print the corresponding trace with function/method names in a text file before bailing out.\n\n* * *",
  "title": "Browser Support • Re: Collection of random crashes",
  "updatedAt": "2026-06-10T10:03:13.000Z"
}