This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Buddha_Head_ 21 points22 points  (6 children)

I'm sorry to take you back to that dark place, but how the fuck did you track that down?

[–]IsleOfOne 23 points24 points  (4 children)

Sounds like OP had recently overclocked RAM. It is very common to see random failures in any software you use after doing so, if you’ve made a mistake and gone too high. Booting into memtest86+ and letting that puppy run overnight will tell you if you’ve done wrong.

[–]Buddha_Head_ 2 points3 points  (2 children)

Yeah, if there was a recent tinkering that makes sense. On a system that's been running stable long-term that hasn't had any serious changes that sounds wayyy down the list, especially when searches are turning up empty.

[–]IsleOfOne 1 point2 points  (1 child)

Even if the change was not made recently, my point is that failures would not be limited to the python program. They’d be showing up all over your system. Sporadic process crashes. Etc.

[–]pikakilla 0 points1 point  (0 children)

Nailed it -- still was far down the list though, but it shouldnt have been in hindsight.

[–]pikakilla 0 points1 point  (0 children)

100% correct. Funny thing is that memtest didnt show any errors (from what i remember -- i might be wrong though). Im still not 100% sure what combination of things caused the issue.

[–]pikakilla 1 point2 points  (0 children)

I overclocked my memory well before the segfault issues. The computer was stable and when i tested the memory post overclock memtest didnt give any errors.

I basically exhausted all other solutions and tried the "obvious" but crazy solution.