February 11, 20197 yr Hi, I recognized these errors in my logs from time to time: Feb 11 06:55:38 server kernel: ffdetect[7993]: segfault at 38 ip 0000000000403a38 sp 00007ffe0bc961a0 error 4 in ffdetect[400000+15000] Feb 11 06:55:38 server kernel: Code: 66 90 48 8b 14 24 48 8d 35 2c a6 00 00 bf 01 00 00 00 31 c0 4c 8d 35 a7 a9 00 00 ff 15 09 42 21 00 48 89 ef ff 15 38 43 21 00 <45> 0f b6 2c 24 45 84 ed 75 4c e9 99 00 00 00 66 0f 1f 84 00 00 00 Feb 11 06:55:38 server kernel: ffdetect[7994]: segfault at 38 ip 0000000000403a38 sp 00007ffc20f107b0 error 4 in ffdetect[400000+15000] Feb 11 06:55:38 server kernel: Code: 66 90 48 8b 14 24 48 8d 35 2c a6 00 00 bf 01 00 00 00 31 c0 4c 8d 35 a7 a9 00 00 ff 15 09 42 21 00 48 89 ef ff 15 38 43 21 00 <45> 0f b6 2c 24 45 84 ed 75 4c e9 99 00 00 00 66 0f 1f 84 00 00 00 Can someone tell me what's going on there please?
February 11, 20197 yr Well, a segfault is a memory access violation. A program is trying to access a memory address that is outside its scope. It's usually caused by a programming error. Now, a quick Google suggests ffdetect might be something to do with Emby Server, so a bug in Emby would be my suggestion, given the lack of other clues.
March 24, 20197 yr On 2/12/2019 at 5:50 PM, Marv said: Ok, thanks for your clarification Hi, may i ask if you use the Ryzen build? Cause i have the same issue. Mar 24 12:26:54 SST-CS01B kernel: ffdetect[4494]: segfault at 38 ip 0000000000403a38 sp 00007ffdf4208d30 error 4 in ffdetect[400000+15000] Mar 24 12:26:54 SST-CS01B kernel: Code: 66 90 48 8b 14 24 48 8d 35 2c a6 00 00 bf 01 00 00 00 31 c0 4c 8d 35 a7 a9 00 00 ff 15 09 42 21 00 48 89 ef ff 15 38 43 21 00 <45> 0f b6 2c 24 45 84 ed 75 4c e9 99 00 00 00 66 0f 1f 84 00 00 00 Mar 24 12:26:55 SST-CS01B kernel: ffdetect[4501]: segfault at 38 ip 0000000000403a38 sp 00007ffc7da7e1b0 error 4 in ffdetect[400000+15000] Mar 24 12:26:55 SST-CS01B kernel: Code: 66 90 48 8b 14 24 48 8d 35 2c a6 00 00 bf 01 00 00 00 31 c0 4c 8d 35 a7 a9 00 00 ff 15 09 42 21 00 48 89 ef ff 15 38 43 21 00 <45> 0f b6 2c 24 45 84 ed 75 4c e9 99 00 00 00 66 0f 1f 84 00 00 00 Edited March 24, 20197 yr by rallos_hoo
May 9, 20197 yr Author On 3/24/2019 at 6:47 AM, rallos_hoo said: Hi, may i ask if you use the Ryzen build? Cause i have the same issue. Mar 24 12:26:54 SST-CS01B kernel: ffdetect[4494]: segfault at 38 ip 0000000000403a38 sp 00007ffdf4208d30 error 4 in ffdetect[400000+15000] Mar 24 12:26:54 SST-CS01B kernel: Code: 66 90 48 8b 14 24 48 8d 35 2c a6 00 00 bf 01 00 00 00 31 c0 4c 8d 35 a7 a9 00 00 ff 15 09 42 21 00 48 89 ef ff 15 38 43 21 00 <45> 0f b6 2c 24 45 84 ed 75 4c e9 99 00 00 00 66 0f 1f 84 00 00 00 Mar 24 12:26:55 SST-CS01B kernel: ffdetect[4501]: segfault at 38 ip 0000000000403a38 sp 00007ffc7da7e1b0 error 4 in ffdetect[400000+15000] Mar 24 12:26:55 SST-CS01B kernel: Code: 66 90 48 8b 14 24 48 8d 35 2c a6 00 00 bf 01 00 00 00 31 c0 4c 8d 35 a7 a9 00 00 ff 15 09 42 21 00 48 89 ef ff 15 38 43 21 00 <45> 0f b6 2c 24 45 84 ed 75 4c e9 99 00 00 00 66 0f 1f 84 00 00 00 Sorry for the late response. I don't use Ryzen. The error is gone for me since some Emby update.
February 12, 20206 yr I'm seeing this too when Emby starts. It's reproducible any time I restart Emby.
September 10, 20205 yr Bump. Segfault issue with Ryzen 1700 here. kernel: ffdetect[13270]: segfault at 38 ip 000000000040412a sp 00007ffc4b423980 error 4 in ffdetect[403000+c000]
September 11, 20205 yr I get the same issue everyday after my Auto Backup finishes and restarts Emby. I've posted on the Emby forums and got nowhere with it. What's strange is that it was gone for a while but the bug was reintroduced with an update a while back. I wish I had paid closed attention to when the error started up again
September 11, 20205 yr Community Expert I'm used to seeing these in several diags, so probably normal.
Archived
This topic is now archived and is closed to further replies.