hyperion.ng: hyperiond crashed with a segfault, but I could not reproduce it
- I confirm that this is an issue rather than a question.
Bug report
For what it’s worth, Up on saving LED Layout (Frame) I changed all non advanced availabe parameters, hyperiond crashed with dmesg
[146030.413167] Effect[6315]: segfault at a9 ip 00007f732a1d3734 sp 00007f731ce439f8 error 4 in libpython3.5m.so.1.0[7f7329feb000+3c5000]
[146030.413174] Code: 48 89 53 f0 48 89 4d 08 48 89 0a 48 89 6b e8 48 83 c8 02 48 89 43 f8 48 83 c4 08 31 c0 5b 5d c3 66 0f 1f 44 00 00 48 8b 47 08 <f6> 80 a9 00 00 00 40 74 33 53 48 8b 80 48 01 00 00 48 89 fb 48 85
I used alpha5
Steps to reproduce
Tryed to to the same, but it didn’t happen
- compile alpha 5 with docker_compile.sh
- install
- configure LED
- save > crash
What is expected?
Shouldn’t segfault I guess
What is actually happening?
Segfaults
System
Hyperion Server:
- Build: master (Paulchen-Panther-2e83c58/e358792-1587148622)
- Build time: Apr 18 2020 07:29:11
- Git Remote: https://github.com/hyperion-project/hyperion.ng.git
- Version: 2.0.0-alpha.5
- UI Lang: auto (BrowserLang: en-US)
- UI Access: default
- Avail Capt: v4l2,framebuffer,x11,qt
Hyperion Server OS:
- Distribution: Ubuntu 19.10
- Arch: x86_64
- Kernel: linux (5.3.0-46-generic (WS: 64))
- Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 19 (10 by maintainers)
Commits related to this issue
- Update bug_report.md https://github.com/hyperion-project/hyperion.ng/issues/772#issuecomment-615870439 — committed to hyperion-project/hyperion.ng by Paulchen-Panther 4 years ago
- Update bug_report.md https://github.com/hyperion-project/hyperion.ng/issues/772#issuecomment-615870439 — committed to Lord-Grey/hyperion.ng by Paulchen-Panther 4 years ago
I would like to point out that hyperion.ng is still in the alpha phase. Since errors can still occur when saving the settings. However, no settings should be missing in the database, so everything is read correctly when hyperion is restarted. If you can, we would be happy to receive a gdb backtrace log. If you are not able to do this, please do not ask how. Ask an internet search engine.
Regards Paulchen-Panther