QNAP TS-531P and emby-server-qnap_3.6.0.76_arm-x41.qpkg

[heath600 Topic Author 0]

The latest email I have received by QNAP 

Per the feedback from our engineering team, the root cause of the segmentation fault might be related to the kernel page size instead of the floating point unit. 

The kernel page size differences between TS-431P and TS-531P are 4K page size v.s. 32K page size.
If they use fixed 4K page size, it might cause the problem. 

Thank you.

Best Regards,
Albert Shan

I did confirm the page file is 32K on my model

#include <stdio.h>
#include <unistd.h>

int main(void)
{
int sz;
sz=getpagesize();
printf("Page size: %d\n",sz);
return 0;
}

That returns 

 

Page size: 32768

 

QNAP's feedback does seem plausible.   Any thoughts on there feedback?

 

I do wonder there justification on increasing the page size on very similar CPU's though

[alucryd 62]

We might have to take this to Microsoft. We're using a Linaro toolchain to build everything, except the dotnet runtime which comes from Microsoft. The Linaro toolchains are designed to work with virtually any ARM chip out there so I'm quite sure page size is handled correctly on our end, the fact that ffmpeg works fine is probably proof enough.

[heath600 Topic Author 0]

@@alucryd

 

Any luck with finding a solution?  Have you reached out to Microsoft?  I checked the Github page for dotnet core and did not see any similar issues to comment on.

 

The latest pack I believe .20 had no change.

[Luke 25097]

@@alucryd

 

Any luck with finding a solution?  Have you reached out to Microsoft?  I checked the Github page for dotnet core and did not see any similar issues to comment on.

 

The latest pack I believe .20 had no change.

 

Hi, we don't have anything new to report yet. We're still looking into it. Thanks.

[Luke 25097]

Can you try our latest betas? It probably won't be any different, but just curious. Thanks.

[heath600 Topic Author 0]

4.2.0.33 still gives the same segmentation fault when trying to launch the application.

[Luke 25097]

Ok, thanks for trying.

[heath600 Topic Author 0]

Updated my QNAP to 4.3.6 and Emby to 4.3.0.8 and still have the same issue.

[Luke 25097]

Ok, thanks for the info.

[heath600 Topic Author 0]

Just tried 4.4.0.4 and still get the same segmentation fault.

 

Has any progress been made with QNAP over the last 3-4 months?

[Luke 25097]

We do have a submission with QNAP in progress to get into their app store, so hopefully they'll reproduce and be able to help us. It's not affecting every single model or there would be more users reporting it, and we'd be able to reproduce ourselves on the models that we have for testing.

[Lepresidente 0]

I have a TS-431X with the same issue as above it has (Annapurna Labs Alpine AL-212 2-core 1.7 GHz) Arm CPU.

Is this not this issue that has been fixed upstream on the dotnet SDK

 

https://github.com/dotnet/coreclr/issues/17043

 

Edited January 9 by Lepresidente

[heath600 Topic Author 0]

I am assuming there still has not been any progress on this at this point?  The latest .11 version still has the segmentation fault.

 

I have started to get a message in the Android TV app that the version of Emby I am running is no longer supported and to update the server.  Since I cannot update from the version I am running this leaves me with the option to hope you don't fully block the android app from my Emby version(And I will have to endure the popup which occurs alot)  or I have to look at buying new hardware which I have no desire to do since my current QNAP runs fine when using the Q mono version.  

 

What are your thoughts on my current situation.

 

Thanks

[Luke 25097]

What version are you on now?

[heath600 Topic Author 0]

3.5.2.0

[Luke 25097]

Is anyone willing to provide SSH access to their NAS so that we can debug on your machine directly? That may allow us to solve this quickly.

If you're interested in helping out please send me a PM. Thanks!