{
  "@context":"https://www.w3.org/ns/activitystreams",
  "type":"Collection",
  "id":"https://epiktistes.com/objects/txjP7CYZqJM/thread",
  "items":[
    {
  "@context":[
    "https://www.w3.org/ns/activitystreams",
    {"Hashtag":"as:Hashtag"}
  ],
  "published":"2023-03-10T14:54:31.948Z",
  "attributedTo":"https://epiktistes.com/actors/toddsundsted",
  "to":["https://www.w3.org/ns/activitystreams#Public"],
  "cc":["https://epiktistes.com/actors/toddsundsted/followers"],
  "content":"<p>...well, for future reference, <code>Invalid memory access (signal 11) at address 0x7ff7b19429f8</code> likely means the application has overrun its stack, especially if the stack trace shows even moderate <em>recursion</em>. </p><p>about the recursion though, this error happened after only <em>5</em> recursive calls (not 50,000) and that caught me off guard. i've been recently conditioned to think the stack only holds primitive values and references (pointers) but crystal, like c and similar languages, lets you pass around structures (instances of <code>struct</code>) <em>by value</em> and those values can be arbitrarily large.</p><p>now i need to figure out how to debug the contents of the stack...</p><p><a href=\"https://epiktistes.com/tags/crystallang\" class=\"hashtag\" rel=\"tag\">#crystallang</a></p>",
  "mediaType":"text/html",
  "attachment":[],
  "tag":[
      {"type":"Hashtag","name":"#crystallang","href":"https://epiktistes.com/tags/crystallang"}
  ],
  "type":"Note",
  "id":"https://epiktistes.com/objects/txjP7CYZqJM"
}

,
    {
  "@context":[
    "https://www.w3.org/ns/activitystreams",
    {"Hashtag":"as:Hashtag"}
  ],
  "published":"2023-03-10T18:37:00.000Z",
  "attributedTo":"https://types.pl/users/beta",
  "inReplyTo":"https://epiktistes.com/objects/txjP7CYZqJM",
  "replies":"https://types.pl/users/beta/statuses/110000434100214400/replies",
  "to":["https://www.w3.org/ns/activitystreams#Public"],
  "cc":["https://types.pl/users/beta/followers","https://epiktistes.com/actors/toddsundsted"],
  "content":"<p><span class=\"h-card\"><a href=\"https://epiktistes.com/@toddsundsted\" class=\"u-url mention\">@<span>toddsundsted</span></a></span> I&#39;m very curious as how you hit the stack that badly. If it&#39;s a legitimate use, likely you could enlarge the stack</p>",
  "attachment":[],
  "tag":[
      {"type":"Mention","name":"@toddsundsted@epiktistes.com","href":"https://epiktistes.com/actors/toddsundsted"}
  ],
  "url":["https://types.pl/@beta/110000434100214400"],
  "type":"Note",
  "id":"https://types.pl/users/beta/statuses/110000434100214400"
}

,
    {
  "@context":[
    "https://www.w3.org/ns/activitystreams",
    {"Hashtag":"as:Hashtag"}
  ],
  "published":"2023-03-10T20:06:13.894Z",
  "attributedTo":"https://epiktistes.com/actors/toddsundsted",
  "inReplyTo":"https://types.pl/users/beta/statuses/110000434100214400",
  "to":["https://www.w3.org/ns/activitystreams#Public","https://types.pl/users/beta"],
  "cc":["https://epiktistes.com/actors/toddsundsted/followers"],
  "content":"<p><a href=\"https://types.pl/users/beta\" class=\"mention\" rel=\"tag\">@beta</a> i'm curious, as well. i've temporarily increased my stack size so that i can finish what i'm working on, but that's not a solution i'd like to have to ship. it happens in the same place in linux and osx, and with different versions of the language, but so far it only happens when i run tests, so it is possible the testing framework is somehow setting things up in a way that triggers it, but that being the solution requires more faith than i have. i can also easily rewrite this code to be iterative instead of recursive, but that feels a bit like giving up too early. i'll definitely pass along anything i find that might be useful! thanks for inquiring!</p>",
  "mediaType":"text/html",
  "attachment":[],
  "tag":[
      {"type":"Mention","name":"@beta@types.pl","href":"https://types.pl/users/beta"}
  ],
  "type":"Note",
  "id":"https://epiktistes.com/objects/1cCbt7Do8jE"
}


  ]
}