Uncaught Exception EVERY TIME Peerblock will NOT start!!! December 12, 2014 12:23AM |
Registered: nine years ago Posts: 16 |
Re: Uncaught Exception EVERY TIME Peerblock will NOT start!!! December 12, 2014 06:20PM |
Moderator Registered: eleven years ago Posts: 531 |
Anonymous User
Re: Uncaught Exception EVERY TIME Peerblock will NOT start!!! March 17, 2015 06:45PM |
Re: Uncaught Exception EVERY TIME Peerblock will NOT start!!! March 17, 2015 07:44PM |
Moderator Registered: eleven years ago Posts: 531 |
Anonymous User
Re: Uncaught Exception EVERY TIME Peerblock will NOT start!!! March 17, 2015 08:02PM |
Re: Uncaught Exception EVERY TIME Peerblock will NOT start!!! March 17, 2015 08:14PM |
Moderator Registered: eleven years ago Posts: 531 |
Re: Uncaught Exception EVERY TIME Peerblock will NOT start!!! March 18, 2015 01:10PM |
Moderator Registered: eleven years ago Posts: 611 |
Quote
#12 bingobon...@gmail.com
...I started to encounter this error last year after some time of operation. Shutdown and reboot the machine and normally all is well. Today I got that error right after starting Peerblock (actually, trying to start as it happens right away).
...I checked the lists and one (Default P2P) is really over 2MB (it's some 2730KB or so). I deleted the file and started Peerblock. And it works. I let it update, it updates the list, downloads the 2,7 MB again and, bang, after closing the update window, you get the same error.
So, it's indeed related to big lists and that's obviously the reason why it happens more and more - lists are getting bigger. Machine has still 1,5 GB free of RAM, so memory can't be an issue. But the parsing of the file may need very much virtual memory allocation for a short time and that maxes it out. Or maybe it calculates the necessary allocation wrong. Anyway, I think you should be able and find this error once you know it's caused by big lists. The error occurs first in mainproc.cpp and then immediately afterwards in updatelists.cpp.