Log In · Register

 
Windows challenge
heyo-captain-jac...
post 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:
 
 
Start new topic
Replies
heyo-captain-jac...
post Oct 12 2009, 10:37 PM
Post #2


/人◕‿‿◕人\
*******

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.
 
mipadi
post Oct 13 2009, 12:40 AM
Post #3


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>
 

Posts in this topic


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members: