sertion at mono-threads.c:1031, condition `info' not met #13813
Comments
|
Can you install lldb or gdb on the machine, and then get a stack? |
|
Guessing it is here: Still a debugger or repro would be nice. :( |
|
The comments in the code seem to somewhat explain the problem, and try workaround it, but then maybe other code forgets to? |
|
was fix? i trouble same too
|
|
No, bug still happens and once every 24+ hours for an idling server…. I have been busy and couldn’t easy change my headless build to include debug information as requested, step by step I am approacing.
… On 13 Jul 2019, at 20.26, romanianstrife ***@***.***> wrote:
was fix? i trouble same too
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#13813?email_source=notifications&email_token=AAKR7ROX7EZ5P6AG3RB4GALP7IF3LA5CNFSM4HDHDYH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3V6IA#issuecomment-511139616>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKR7RPIA5Y6WPATQZU4BGLP7IF3LANCNFSM4HDHDYHQ>.
|
|
I get this constantly, any workaround? I'm running nUnit tests from the latest Rider (2019.3) via Ubuntu 19.04. |
|
Rolling back to Rider 2019.2.3 solved it (one click via Jetbrains Toolbox) |
|
Many different codepaths end up at (If you installed Mono using a package manager, you may also need to install the As a workaround you can set the environment variable Also I should mention that over the past several months we've fixed a number of bugs related to this assertion (as I said, the assertion is like the final symptom of a variety of underlying bugs), so if you haven't tried a recent official package of Mono you may want to give it a try. For folks using Unity, you don't have the luxury of updating Mono independently, although the Unity team does regularly update their copy of Mono to include upstream bugfixes. As far as I know, Unity's Mono should also dump a stack trace if you install |
Also seeing this with Rider 2019.3.1 on Debian Buster, every time I run my project unfortunately... It seems to happen on multiple projects for me. Luckily, this happens after the process is done, so it's perhaps more of an annoyance than a huge problem. Only when running with debugger attached. No debugger => no assertion failure. |
|
Downgrading to Rider 2019.2.4 seems to have "fixed" the issue for now for me as well. |
Any instructions on how to install lldb or gdb, build on Unity 2017.4 (OSX) for Linux server (headless)? |
|
Seemingly still present in Rider 2020.1 EAP, but with a slightly different error: Someone ought to report this to @JetBrains, otherwise we are likely to retain this problem in the 2020.1 final release as well. 😢 |
we are experiencing a critical threading crash with Mono / Unity 2017 on Linux, does anyone know if this been fixed in newer version? or what makes it unstable?
Platform:
Stacktrace:
The text was updated successfully, but these errors were encountered: