What is the Year 2038 problem?

[Ink]

"The Year 2038 problem is an issue for computing and data storage situations in which time values are stored or calculated as a signed 32-bit integer" - Wikipedia

Short Answer:

"Y2038 refers to an issue related to the way time is handled by computers. Time is often represented as the number of seconds since Jan 1, 1970. Whenever a 32-bit signed integer is used for this, the maximum value that can be represented is +/- ~68 years, 19 days from the epoch, which corresponds to Jan 19, 2038. What happens after that is system dependent, but generally not good. A computer may act as if its time got reset to Dec 1901, or possibly to the epoch of Jan 1, 1970. It may give unexpected results or crash.

Basically, any software that uses time in any way may potentially have Y2038 issues. While only a small percentage of each software component is typically affected, this is still enough to cause many problems. Embedded systems with 32-bit cores and computers running 32-bit versions of Linux and Windows and are particularly at risk, but even 64-bit computer systems may have problems. In 64-bit computer systems, time can be represented in 64-bit integers, but Y2038 issues may still exist in applications, device drivers, databases, storage systems, and network protocols."​

Resources:
i) FAQ - y2038.com
ii) Year 2038 problem - Wikipedia, the free encyclopedia

Hidden egg, can you spot it?

 

[DardiM]

Thanks for the share

That reminds me the famous "Year 2000 bug" : and the fear before this famous date.

 

[hjlbx]

That reminds me the famous "Year 2000 bug"

Yeah, I remember back then some people saying that the 2000 bug would bring and end to the world... LOL.

 

[Noxx]

Yea, heard of the 2000 bug, but not the 2038.

 

[frogboy]

Y2K all over again.

 

[juhful]

The only problem with 2038 is I will be 74 years old lol

 

[LASER_oneXM]

...yep.....same problem again: "Y2K". We will all die again.....

 

[DardiM]

The only problem with 2038 is I will be 74 years old lol

I've got a 83 years old neighbor that can still use his PC (internet or other activities)
(I think I won't talk to him about this problem )

 

[frogboy]

The only problem with 2038 is I will be 74 years old lol

Hopefully in 2038 i will be two years older than you.

 

[DJ Panda]

I knew about the 1970 apple bug the rest is pretty cool! Thanks for the share.

 

[Cohen]

I had no idea about this, very interesting. Thanks for sharing.

 

[Viking]

The Y2K bug didn't cause an apocalypse, and in 2038, it still wont imho

 

[Solarlynx]

I think we still have time to have the bug fixed.

 

[yashiscool]

Very interesting information. Thanks for Sharing. I am sure to be on the x64 bit side all the way.

 

[ravi prakash saini]

After Y2K I do not think it is a bug or deliberately written code,I have come across time related problem in at least two well known GPS processing software,when contacted the vendor ,they said we have to buy new version . However,we managed to find the solution ,keeping in mind that when our team with no IT background can find the solution so can the vendor.
But if the vendor provides the solution ,how he is going to make money and if he leaves some bug in his software that too is bad for his business,so the solution is Y2K types of bug where no one blames the vendor

 

[jamescv7]

Still a long year which any improvements, fixes and even creation of new technology will remove that possible Y2038 problem.

Our technology is already at fast pace adjustment.