PeerBlock 1.0 Crashes Windows XP while running on less than 512 bm ram

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install PeerBlock 1.0 on XP 32 bit system with
   less than 512 mb ram, i was running on:
   Windows XP 32 bit with 256 MB ram.
2. After install, restart computer
3. when windows starts up it restartes after
   a couple of minutes. 
   then peerblock gives an error message
   and says reported to phoenix labs.

What is the expected output? What do you see instead?

I dont know what system requirements need to be for
peerblock to work right, maybe ths needs to be specified
on downloads page. But from this experence i think it wont run
on a XP system with less than 512 mb ram. 
when i upgraded the computer to 512 bm ram, windows and peerblock
started working fine.

What version of PeerBlock are you using? On what operating system? 32- or
64-bit?

PeerBlock 1.0 - Windows XP 32 Bit
This test was on a system with only 256 mb Ram
Upgrading to 512 MB ram seemed to fix the issue.

Please provide any additional information below.  Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.

Problem is fixed now that i am running on 512 mb ram.
I just thought you guys should know that PeerBlock
won't run on a system with less than 512 mb ram.
maybe in future builds PeerBlock should Warn / Block
a user from installing on a system with less than 512 mb ram.

Due to installing / uninstalling peerblock mutiple times before 
i figured out that it was causing the problem, i don't have any
screenshots or dump file or log file. thats why i have mad sure 
i have described the issue in as much detail as i can.

Original issue reported on code.google.com by computer...@gmail.com on 3 Oct 2009 at 2:38

[GoogleCodeExporter]

here is a screen shot of the error message

Original comment by computer...@gmail.com on 3 Oct 2009 at 6:19

Attachments:

• screen.JPG

[GoogleCodeExporter]

As progress goes on and RAM becomes cheaper and cheaper this problem should 
dwindle
away by itself.

Original comment by frederic...@gmail.com on 3 Oct 2009 at 9:12

[GoogleCodeExporter]

Another idea: Add "System Requirements" - I would gladly add them to the 
wikipedia
article.

Original comment by frederic...@gmail.com on 3 Oct 2009 at 9:14

[GoogleCodeExporter]

Thanks for the problem report!  Just to make sure, it's only PeerBlock that's
crashing - not Windows itself - right?  i.e. no "Blue Screen of Death"?  

I'm actually kind of surprised here, we shouldn't be using very much memory...  
Maybe
only during list cache generation?

We definitely should come up with System Requirements type of page; I'll setup 
a VM
to restrict the amount of memory allocated to an XP install, to see where the 
"sweet
spot" is.

Original comment by peerbloc...@gmail.com on 3 Oct 2009 at 6:06

• Changed state: Accepted

[GoogleCodeExporter]

Windows Vista and upwards will completely eradicate this problem by themselves 
:)
http://en.wikipedia.org/wiki/Windows_vista#Hardware_requirements

Original comment by frederic...@gmail.com on 3 Oct 2009 at 8:00

[GoogleCodeExporter]

it was windows xp crash caused by peerblock. 
because of low ram only 256mb, upgrading to 512 mb
fixed the problem.

Original comment by computer...@gmail.com on 4 Oct 2009 at 6:46

[GoogleCodeExporter]

Understood. What I meant by my posting was: If more and more people switch to 
Vista
or 7, they won't encounter your problem because 512mb RAM are the bare minimum 
to run
Vista.

Original comment by frederic...@gmail.com on 4 Oct 2009 at 7:03

[GoogleCodeExporter]

Ooh, sorry to hear it was an actual OS Crash.  In reality this means we could
potentially crash the OS anytime we experience a low-memory situation - for 
example
if you're using 5.9 GB of RAM on your 6 GB system.  Then again, the OS should 
be able
to page out most of that 5.9 GB to disk, whereas in-user kernel-memory not so 
much...

Either way, we 1) shouldn't be crashing the OS if we experience a low-memory
condition, and 2) we shouldn't be sucking up hundreds of megs of memory in any 
event.

Original comment by peerbloc...@gmail.com on 6 Oct 2009 at 2:44

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I may add: Win2000, 128Mb, P3@667MHz, peerblock crashes on startup while 
generating
list cache.

Original comment by giga.cam...@gmail.com on 2 Feb 2010 at 7:59