Nicotine+ 3.3.2 Crash on Value: 'int' object has no attribute 'time_elapsed' about nicotine-plus HOT 7 CLOSED

@slook yes, I haven't run the test yet, but decided to locate the faulty RAM plank, because I suspected that one of four planks (of same model) had issues. I've tried different configuration (running on 1 plank or 2 kits, mixing the pairs) and as of now - I've found the combination where I've got rid of those errors. Nicotine+ is running for 4 days, works as expected.

I suggest to close this ticket. However, I don't have a valid explanation what was the exact rootcause of the RAM issues on my side and why it was fixed in a such a naive way. Anyway, I'm happy that the issue is gone and thank you for your patience and investigation.

from nicotine-plus.

This is not a programming error:

If transfer was actually an integer, Nicotine+ would've crashed on line 495.

Since this issue is essentially the same as your previously reported issues, it seems increasingly likely that this is either a

1. hardware issue, most likely memory, or
2. something outside Nicotine+ screwing with memory

from nicotine-plus.

@501NotImplemented If possible, I suggest checking any files downloaded/modified in recent weeks for any obvious glitches/corruptions.

from nicotine-plus.

@501NotImplemented I am glad you seem to have found the underlying hardware fault in your machine as a result of these investigations, and also thankful for you for providing debug logs and data that has helped make improvements.

However, I don't have a valid explanation...

That is just the nature of hardware failures, by its nature it is frustrating to troubleshoot.

Echoing as above I share the concern about file corruption that may still exist on your system, it would be a good idea to refrain from sharing until you have verified the integrity of your files.

from nicotine-plus.

Could you try the Windows Memory Diagnostic Tool again, as well as MemTest86?

https://www.memtest86.com/
https://www.youtube.com/watch?v=EDCk04hgVEk

Have you run into any BSODs or crashes in other programs?

from nicotine-plus.

@mathiascode I've had BSOD's previously, which were resolved by OS reinstall. Haven't caught them since then. I'll try to rerun Win Memory Diagnostic again on the weekends, last time it didn't find any issues, but it's a quite time-consuming check.

from nicotine-plus.

Have you had opportunity to verify that you don't have faulty RAM in your machine?

Also, another test (that is quicker do) that can be run is does a SMART data check pass on your hard drive(s)?

from nicotine-plus.