History Main / MillenniumBug

The Millennium Bug is one of the more famous examples of an OverflowError. For the sequel to the Bug itself, watch for the [[http://en.wikipedia.org/wiki/Year_2038_problem Year 2038 problem]] (when the [-Platform/{{UNIX}}-] system time integer exhausts its [[UsefulNotes/BinaryBitsAndBytes 32 bits]]). Fortunately, by that point, we'll certainly be using 64-bit time;[[note]]And we won't have to worry about THIS issue until the year [[TimeAbyss 292,277,026,596]].[[/note]] however, many embedded systems still use 32-bit time as of now. Due to increasingly rapid change of digital technology, especially on embedded systems, they tend to be replaced for low prices (or in the case of offline museum material, have the time rewinded). And if you're willing to wait ''much'' longer, refer to the Year 10000 problem, as clocks aren't used to handling five digit year numerals.

* ''VisualNovel/SteinsGate'' has this happen in some of the timelines that Okabe sees.

* The original ''[[VideoGame/BackyardSports Backyard Baseball]]'' also contains a [=Y2K=] bug. Upon beating the game, your name will be entered into the Hall of Fame with a date on the achievement as well, with the date written in a MM/DD/YY format. If an award is obtained and your computer's internal clock is any day past 1999, it will instead read as MM/DD/(Year-1900). So, if you won it on, say, January 15, 2003, it would read as 1/15/103. Curiously, the team photo doesn't suffer from any such bug, correctly displaying the year as "[=20XX=] Team Photo". Even more oddly, the record book ''also'' doesn't have this problem, despite using the ''exact same date format'' as the Hall of Fame!

[[folder:Films -- Animated]]

* The upcoming film ''[=Y2K=]'' is a comedy about a WildTeenParty on New Years' Eve 1999 in which the [=Y2K=] bug turns out to be real and blacks out the world.