Segmentation Fault - Possible bug Ubuntu

[adis99]

Tried installing latest version, application keeps crashing randomly.

Occasionally it will run for 5-10 minutes and then die, most of the time it just dies automatically

Attaching valgrind, dumps, and manual run outputs.

Coredump (too large) avail here:
https://wetransfer.com/downloads/13596666145cc3d61f857c8c8c776db220210918145619/f369225674232bfa3caeb11d82390dd720210918145631/7bd542
or here:
https://www.dropbox.com/s/s6um9yqxhunxcd...x.zip?dl=1

[mvallevand]

There is nothing there that describes your configuration. I personally won't analyze linux dumps but I can look at your NextPVR logs and journalctl/dmesg output for clues to help you.

Martin

[adis99]

There is nothing there that describes your configuration.  I personally won't analyze linux dumps but I can look at your NextPVR logs and journalctl/dmesg output for clues to help you.

Martin

Added, also take a look at verbose valgrind output, it specifically mentions bug in application.



disInstr(thumb): unhandled instruction: 0xF1A4 0x0D50
==22309== valgrind: Unrecognised instruction at address 0x5a7c2bd.
==22309==    at 0x5A7C2BC: _DacGlobals::InitializeEntries(unsigned int) (in /opt/dotnet/shared/Microsoft.NETCore.App/3.1.19/libcoreclr.so)
==22309== Your program just tried to execute an instruction that Valgrind
==22309== did not recognise.  There are two possible reasons for this.
==22309== 1. Your program has a bug and erroneously jumped to a non-code
==22309==    location.  If you are running Memcheck and you just saw a
==22309==    warning about a bad jump, it's probably your program's fault.
==22309== 2. The instruction is legitimate but Valgrind doesn't handle it,
==22309==    i.e. it's Valgrind's fault.  If you think this is the case or
==22309==    you are not sure, please let us know and we'll try to fix it.
==22309== Either way, Valgrind will now raise a SIGILL signal which will
==22309== probably kill your program.

[mvallevand]

I would suspect the issue is dotnet on Exynos armv7 not NextPVR. I know users have had issues with it. Do you see anything like this https://forums.nextpvr.com/showthread.ph...#pid555287

If you can install Docker you might have more luck.

Martin

[adis99]

I would suspect the issue is dotnet on Exynos armv7 not NextPVR.  I know users have had issues with it.  Do you see anything like this https://forums.nextpvr.com/showthread.ph...#pid555287

If you can install Docker you might have more luck.

Martin

mine is little different :

root@plex:/opt# cat /proc/cpuinfo | grep Features
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm

[mvallevand]

At least it is not 16bit. I'd research running dotnet on that device. I haven't installed the arm32 bit for this release yet so it is possible that the packaging isn't correct. If you have an RPi or other device you could let us know.

Martin

[adis99]

At least it is not 16bit.  I'd research running dotnet on that device.  I haven't installed the arm32 bit for this release yet so it is possible that the packaging isn't correct.  If you have an RPi or other device you could let us know.

Martin

I use Odroid Home Cloud One. I'll do some digging on my side too

[mvallevand]

Installing on CoreElec and LibreElec is on my todo list.

Martin

[adis99]

Installing on CoreElec and LibreElec is on my todo list.

Martin

I actually have 20.04 on it :
https://wiki.odroid.com/odroid-xu4/os_im...inux/start

Mainly using it for plex, but wanted to integrate nextpvr to do iptv recordings/scheduling and dump to Plex repo

[adis99]

I found something interesting here.

I rebooted to clear state fully, service is running. when I access it using private window in chrome it has no issues and doesnt crash.
But when I use non-private (also chrome) it crashes quickly. One thing that i suspect is that I use NextPVR on my windows box too which i access with non private and it could be somehow confusing sessions/cookies.

I'll keep testing that