Ha, ya, thanks Benoit. I'm not sure what that was about, but here's the real values (I think): ``` (gdb) rp i FIXNUM: 15 ``` ``` (gdb) rp values[14] FIXNUM: 70068055741204 (gdb) rp values[15] FIXNUM: 286326800 (gdb) rp ...travisbell (Travis Bell)
Benoit_Tigeot (Benoit Tigeot) wrote in #note-23: > The "good" news, is I am able to reproduce at 100% if I use concurrency. For what it's worth on #21034, that environment is a Falcon environment so yes, concurrency is in play there as ...travisbell (Travis Bell)
alanwu (Alan Wu) wrote in #note-10: > Curious if you get this crash without YJIT? I can confirm, if I disable YJIT, the crashes seem to stop happening.travisbell (Travis Bell)
Hi Alan, I haven't tried to be honest. Let me deploy now with it disabled and I will let you know. It reliably happens within minutes so it's very easy to check.travisbell (Travis Bell)
Awesome! Thanks for the how to. Really appreciate it. Alright, here's the results; ``` (gdb) frame 13 #13 rb_gc_mark_vm_stack_values (n=64, values=0x7f26022c0000) at gc.c:2346 warning: 2346 gc.c: No such file or directory ``` ...travisbell (Travis Bell)
Thanks Aaron. This is a bit out of my wheelhouse. Here, I've got a new backtrace: ``` (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_intern...travisbell (Travis Bell)
Here's a crash dump: https://gist.github.com/travisbell/fc3b03a5d1bd797e16e990c17fb2ec9a Based on what I am seeing here, I think it is the same crash as [21021](https://bugs.ruby-lang.org/issues/21021) (do you agree?) If so, feel free...travisbell (Travis Bell)
Could be related to the issue posted here: https://bugs.ruby-lang.org/issues/21021 but I am not using ActiveJob so hard to say if we're crossing the same paths or not.travisbell (Travis Bell)
Hi everyone, I noticed we started having some workers crash after upgrading to 3.4.1. I tried grabbing a core file and got this output. Is it enough to figure out what's going on? If not, I can reproduce this fairly easily, so I can g...travisbell (Travis Bell)
travisbell (Travis Bell)04:07 PM Ruby Bug #21034: try to mark T_NONE object error after upgrading to 3.4.1