Timeline for Geth 1.6.1 hangs throwing "unexpected fault address" fatal error
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 18, 2018 at 0:06 | comment | added | Linas | Beats me. I notice you commented on github. I can't tell if your new stack trace is the same as the old one. If you have a different stack trace, you should open a different issue. It gets very confusing, very quick, if the same github issue is used to report different problems. The original crash was always in memmove, in hashimoto. Your crash seems to be in a different place. | |
| Feb 16, 2018 at 22:36 | comment | added | Fred Douglis | @Linas, can you please be more specific about the fix? I just cloned and built geth and am running into the core dump today -- though I can't guarantee it's identical to that reported here. | |
| Feb 10, 2018 at 6:11 | comment | added | Linas | I think I saw a comment float by, stating that this was recently fixed (circa January 2018) | |
| Nov 27, 2017 at 8:33 | comment | added | Juan Ignacio Pérez Sacristán | Yes, it's true. My nodes running 1.7.2 hang once a day or so when mining | |
| Nov 27, 2017 at 4:49 | review | Late answers | |||
| Nov 27, 2017 at 9:48 | |||||
| Nov 27, 2017 at 4:34 | review | First posts | |||
| Nov 27, 2017 at 7:58 | |||||
| Nov 27, 2017 at 4:33 | history | answered | Linas | CC BY-SA 3.0 |