Windows challenge |
  |
 Oct 12 2009, 10:21 PM
Post
#1
|
|
 /人◕‿‿◕人\  Group: Official Member Posts: 8,283 Joined: Dec 2007 Member No: 602,927  |
ITT: we see how many programs we can run before our system starts becoming unusably slow.
mine: 
|
|
|
|
|
Oct 12 2009, 10:22 PM
Post
#2
|
|
 kthxbai Group: Official Designer Posts: 2,832 Joined: Feb 2008 Member No: 621,203 |
I wouldn't even know where I would find 1039 processes on my computer.
I currently have 49 processes running....... I turned on everything that I knew of. |
|
|
|
|
Oct 12 2009, 10:24 PM
Post
#3
|
|
|
/人◕‿‿◕人\ Group: Official Member Posts: 8,283 Joined: Dec 2007 Member No: 602,927 |
I used a batch file to run notepad.exe 1000 times. I normally only have 39 running.
|
|
|
|
|
Oct 12 2009, 10:28 PM
Post
#4
|
|
|
kthxbai Group: Official Designer Posts: 2,832 Joined: Feb 2008 Member No: 621,203 |
Could you tell me how to do that? I want to know how many my computer can handle.
|
|
|
|
|
Oct 12 2009, 10:37 PM
Post
#5
|
|
|
/人◕‿‿◕人\ Group: Official Member Posts: 8,283 Joined: Dec 2007 Member No: 602,927 |
You can try just a regular fork bomb, they're fairly simple. Just time how long it takes your computer to memory overflow.
CODE @ECHO OFF :A START notepad.exe START fork.bat GOTO A Paste that into notepad, and save it as fork.bat Be sure it doesn't save as fork.bat.txt, because then it's not going to work. |
|
|
|
|
Oct 12 2009, 10:39 PM
Post
#6
|
|
|
kthxbai Group: Official Designer Posts: 2,832 Joined: Feb 2008 Member No: 621,203 |
gracias.
|
|
|
|
|
Oct 12 2009, 10:41 PM
Post
#7
|
|
|
/人◕‿‿◕人\ Group: Official Member Posts: 8,283 Joined: Dec 2007 Member No: 602,927 |
By the way, I don't know why you would want to forkbomb your computer.
|
|
|
|
|
Oct 12 2009, 10:48 PM
Post
#8
|
|
|
kthxbai Group: Official Designer Posts: 2,832 Joined: Feb 2008 Member No: 621,203 |
|
|
|
|
|
Oct 13 2009, 12:40 AM
Post
#9
|
|
 Senior Member Group: Administrator Posts: 2,648 Joined: Apr 2008 Member No: 639,265 |
QUOTE(Buttsex @ Oct 12 2009, 11:37 PM)  You can try just a regular fork bomb, they're fairly simple. Just time how long it takes your computer to memory overflow. I know this is pedantic, but a fork bomb doesn't cause problems because memory is used up; it causes problems because the OS's process table becomes filled (not because of memory constraints, just because the process table only holds a finite number of processes). I think Windows uses a shared, copy-on-write memory model (I know Unix/Linux/Mac OS X does), so 1 notebook.exe process uses roughly the same amount of memory as 1,000,000. </systems-programmer> |
|
|
|
|
Oct 13 2009, 03:35 PM
Post
#10
|
|
|
/人◕‿‿◕人\ Group: Official Member Posts: 8,283 Joined: Dec 2007 Member No: 602,927 |
Except the thousand I had running used 70% of my memory, while with only one open I was using 20% of my memory.
|
|
|
|
|
Oct 13 2009, 03:59 PM
Post
#11
|
|
|
Senior Member Group: Administrator Posts: 2,648 Joined: Apr 2008 Member No: 639,265 |
Perhaps Windows' copy-on-write mechanism is more conservative than that of Unix and Linux. At any rate, a fork bomb works by filling up the process table (which maps a process to its virtual memory space), and not by using up RAM itself.
|
|
|
|
|
Oct 13 2009, 04:30 PM
Post
#12
|
|
|
/人◕‿‿◕人\ Group: Official Member Posts: 8,283 Joined: Dec 2007 Member No: 602,927 |
I suppose that could be it.
|
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members: