Jump to content

4.6.4.0 causes random mono core dumps on FreeBSD 13


Recommended Posts

Posted (edited)

Anyone else seeing this?

 

I cant find anything in the Emby logs, although what appears to be a random amount of time of playback my Emby service just crashes in my jail.

Maybe also not specific to FreeBSD 13, some on FreeBSD 12 with the same problem?

Edited by Duffyx
Posted

Hi, how did you install emby server?

Posted

FreeBSD ports

Posted

Can you please attach the emby server log from when this happened? Thanks.

adrianwi
Posted

I've already reported this as a problem with a Photo library

 But have also seen more random shutdowns on 4.6.4.0 than I'd ever experienced with previous versions. 

Posted

I think using a newer version of the mono runtime could potentially help:

 

adrianwi
Posted

Going to try this and will let you know...

  • Thanks 1
Posted

Using the newer mono runtime does not help.

Posted
1 hour ago, Duffyx said:

Using the newer mono runtime does not help.

Can you please attach an emby server log? Thanks.

  • 2 weeks later...
Posted (edited)

As a last resort I deleted my full /var/db/emby-server directory and started fresh. That seems to have worked for now, stable playback, no more core dumps. Luke is it possible the database got ripped with an update that wasn't fully finished (converted the database)?

Edited by Duffyx
Posted
5 hours ago, Duffyx said:

As a last resort I deleted my full /var/db/emby-server directory and started fresh. That seems to have worked for now, stable playback, no more core dumps. Luke is it possible the database got ripped with an update that wasn't fully finished (converted the database)?

It's hard to say at this point but I"m glad to hear you're seeing better results. Ultimately I think the issues are tied to having to use the mono runtime rather than the .net core runtime.

Posted (edited)

But both are equally supported I hope? Given FreeBSD does not have .NET yet.

Edited by Duffyx
Posted

Yes, we do the best we can with the mono runtime but occasionally there are times when we run into it's limitations and can't do anything about it. For example, the inability to use the realtime monitor, higher resource consumption, etc.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...