Just found this little file on one of my storage drives, and remember having a bit of fun with it years ago

The file is a tiny 78kB, extract it using 7zip to find the extracted file is now 21MB, now extract that file and you`ll see that the extracted file is now 2.8GB

How many times can you extract Googolplex before you or your machine gives up ?

Apparently there is a file hidden at the very end of all of the extractions but I have never managed to get that far, from what I remember it is a text file containing the entire numerical value of a Googolplex

You don't suddenly get 100 Petabytes trying to decompress, each time you extract the file it gets bigger and offers no harm to the machine at all, it doesn't try to crash your system whatsoever

Yes, if you manually extract it the file doesn't expand until you initiate the next nested level, but the the same wouldn't be true for an AV program. For the AV it would initiate the next step automatically in order to ensure the contents of the file are safe. As a result, it would continue going down a level until it exploded.

Assume a text file with 1 byte per character, the numerical value of a Googolplex would be (1e100) + 1 bytes which is ten duotrigintillion bytes or 9.095e87 terabyes. There isn't enough digital storage on earth to hold this value.

"VirusTotal is a website that provides free checking of files for viruses. It uses up to 44 different antivirus products and scan engines"-wikipediahttps://www.virustot...5333d/analysis/File name: googolplex.gzDetection ratio: 0 / 32

Yes, if you manually extract it the file doesn't expand until you initiate the next nested level, but the the same wouldn't be true for an AV program. For the AV it would initiate the next step automatically in order to ensure the contents of the file are safe. As a result, it would continue going down a level until it exploded.

There are no file extensions on any of the nested levels, probably to prevent that happening

I just tried expanding the first level (which produced several .zip files) and Windows (SearchFilterHost.exe) started using all my 8GB of RAM.
I had to terminate the Search Indexer process and then delete the .zip files via the command line.