This discussion was created from comments split from: Task Error: Object reference not set to an instance of an object.
Latest dev build crashed while using this “search all missing”
[Info] ParsingService: Using Scene to TVDB Mapping for: XXXXXX - Scene: 4x20 - TVDB: 5x20
Stacktrace:
Native stacktrace:
mono() [0x4a9b01]
mono() [0x50058f]
mono() [0x41f477]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfbb0) [0x7fa161df5bb0]
mono() [0x5ec06b]
mono() [0x5ed279]
mono() [0x5c92d7]
mono() [0x5cecc6]
mono() [0x5cf288]
mono() [0x5e54d4]
mono() [0x5e57ab]
[0x4161b250]
Debug info from gdb:
Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
Aborted (core dumped)
Also, seems to be spamming a lot of the below message in the logs before it crashed.
"[Info] ParsingService: Using Scene to TVDB Mapping for:"
@a1005606 moved to a new thread as it is not related to the other issue.
What version of mono are you running?
3.2.1 (Debian 3.2.1+dfsg-1~pre3+raring2)
Could you provide the whole log around the time of the crash? Looks like mono 3.2 still has threading issues, unfortunately, at this point there isn’t much we can do except try to gather more information.
Last 40+ messages in the log was “[Info] ParsingService: Using Scene to TVDB Mapping for:”
Would it be a good idea to try Mono 3.4?
Those are just informational, Trace logging would be helpful: https://github.com/NzbDrone/NzbDrone/wiki/Log-Files
Not sure about 3.4, I haven’t looked at it myself.
Running 3.2.8 fixed the issue.