From: Eric Wong Date: 2018-12-17T06:03:03+00:00 Subject: [ruby-core:90583] Re: [Ruby trunk Bug#15424] Ruby 2.6.0rc1 & 2.6.0rc2 mutex exception mat999@gmail.com wrote: > /.../config/application.rb:107: [BUG] invalid keeping_mutexes: Attempt to unlock a mutex which is locked by another thread > ruby 2.6.0rc2 (2018-12-15 trunk 66408) [armv8l-linux-eabihf] Are you able to replicate this on x86 or x86-64? Also, is this glibc, musl or some other userspace C library? I don't have access to other hardware, haven't tried QEMU in a while and not sure how slow it is for me. > Last known working version 2.6.0preview2 OK, thanks. It helps us narrow it down. Can you try "git bisect"? > I've tried but the only way I can replicate it is a > combination of fork and the rails active record connection > system. Can you reproduce it on sqlite and perhaps share a standalone repo? I haven't setup postgres or mysql in years, now. > I'm likely missing something in understanding the replicating > factor, something rails specific. It may just be down to threads and mutexes... It's generallly a bad idea to fork w/o immediate exec while Threads are already running. Ruby supports it right now because of some nasty hacks (GVL), but maybe we won't be able to in the future. Unsubscribe: