onyx has quit [Read error: Connection reset by peer]
notzmv has quit [Ping timeout: 272 seconds]
hightower3 has joined #crystal-lang
hightower2 has quit [Ping timeout: 268 seconds]
notzmv has joined #crystal-lang
_ht has joined #crystal-lang
dannyAAM has quit [Remote host closed the connection]
dannyAAM has joined #crystal-lang
ur5us has joined #crystal-lang
brw3 has joined #crystal-lang
brw has quit [Ping timeout: 255 seconds]
brw3 is now known as brw
brw has quit [Quit: Ping timeout (120 seconds)]
brw has joined #crystal-lang
wolfshappen has quit [Quit: later]
Sankalp has quit [Ping timeout: 260 seconds]
Sankalp- has joined #crystal-lang
Sankalp- is now known as Sankalp
brw has quit [Quit: Ping timeout (120 seconds)]
brw has joined #crystal-lang
Sankalp has quit [Ping timeout: 272 seconds]
hightower3 has quit [Ping timeout: 272 seconds]
hightower2 has joined #crystal-lang
hightower3 has joined #crystal-lang
hightower3 has quit [Read error: Connection reset by peer]
hightower2 has quit [Ping timeout: 268 seconds]
wolfshappen has joined #crystal-lang
hightower2 has joined #crystal-lang
jmdaemon has quit [Ping timeout: 264 seconds]
hightower2 has quit [Read error: Connection reset by peer]
hightower2 has joined #crystal-lang
ur5us has quit [Ping timeout: 272 seconds]
renich has joined #crystal-lang
notzmv has quit [Ping timeout: 272 seconds]
<FromGitter>
<lebogan> after some searching, found issue #11497 which addresses my previous issue. Think I'm going to back off for now since I do have 1.1.1 working on Rasbian Buster 32-bit. I need to do more research, maybe try on 64-bit os for pi? Thanks @Blacksmoke16 .
<FromGitter>
<RespiteSage> You get an invalid memory access.
<FromGitter>
<RespiteSage> But if you change the exponent to 2*28 or 2*30 then it's just an arithmetic overflow.
<FromGitter>
<RespiteSage> 1) `2**28` or `2**30`
<FromGitter>
<RespiteSage> \* \*
<FromGitter>
<RespiteSage> And it's only ever an overflow error on my machine.
<FromGitter>
<RespiteSage> My guess is that there's a sweet spot in the Hash initial capacity where the number is too small to cause an overflow before memory allocation and large enough to cause an overflow after memory allocation and that the allocated memory is more than carc.in is providing. Does anyone else have any idea if that's right?