Open loki42 opened 2 years ago
I managed to repro what was maybe this.......... when I wasn't in the debugger. Classic.
Still have that core file? Backtrace?
I'll try and generate one again... Ubuntu cunningly doesn't generate cores when you've told ulimit to generate them... I now need to look at the "app reporter".... arg.
I'll probably catch it eventually, but figured I'd ask.
I'll need to recompile with debugging, but I've worked out how the Ubuntu core dump thingy works:
Program terminated with signal SIGSEGV, Segmentation fault.
[Current thread is 1 (Thread 0x7ff0a84b6700 (LWP 11879))] (gdb) bt
from /usr/lib/libingen_server.so
Nice, thanks.
... yaaay destruction crashes. Those are always "fun".
Er, no, I got confused by the type. Probably a race.
Give me a yell if you're having trouble reproducing it and I can upload a trace from a debug build. It doesn't happen every time so I'm assuming race.
On Fri, 23 Sept 2022 at 04:33, David Robillard @.***> wrote:
Er, no, I got confused by the type. Probably a race.
— Reply to this email directly, view it on GitHub https://github.com/drobilla/ingen/issues/32#issuecomment-1255403013, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAISQBD46OSQLJLUUPWYPDDV7SRBHANCNFSM6AAAAAAQQXZUFI . You are receiving this because you authored the thread.Message ID: @.***>
Won't hurt, but I've ended up on a tangent struggle with sanitizers not working on my machine for some reason. I suspect tsan will show something here a lot more easily than trying to figure it out manually...
Heading away for the weekend though, so I'll have to pick this one up again on Monday.
I care more about bypass from midi but if you're in a bug fixing mood give me a yell if you need help reproducing this deletion bug or if it's fixed and we can close it.
On Sun, 25 Sept 2022, 1:09 am David Robillard, @.***> wrote:
Won't hurt, but I've ended up on a tangent struggle with sanitizers not working on my machine for some reason. I suspect tsan will show something here a lot more easily than trying to figure it out manually...
Heading away for the weekend though, so I'll have to pick this one up again on Monday.
— Reply to this email directly, view it on GitHub https://github.com/drobilla/ingen/issues/32#issuecomment-1256991009, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAISQBBHEBMYZPDK7UMHEP3V74KS7ANCNFSM6AAAAAAQQXZUFI . You are receiving this because you authored the thread.Message ID: @.***>
I've managed to kind of reproduce it sometimes maybe, but life got in the way. I think it has something to do with the locking not going "high enough", to protect changes to the parent graph as well (this is the only case where changing something in a graph mucks with the process order and so on of the parent). A reliable repro would certainly be nice, but I'm not super blocked on it.
Hopefully will have more free time in the fall to figure this one out...
Using the ingen -ed normal desktop build on x86 (AMD64) segfault if you delete an input or output of a sub graph. Doesn't always happen though.
Example file attached.
main.txt
_:b159 a patch:Delete ; patch:sequenceNumber "83"^^xsd:int ; patch:subject </main/main/loop_common_in_1> .
_:b160 a patch:Delete ; patch:sequenceNumber "84"^^xsd:int ; patch:subject </main/main/loop_common_out_1> .
Segmentation fault (core dumped)