If you are like me, you may use a calculator such as the Windows Calculator on a regular basis. I just discovered a bug while working on a project that appears to have been introduced with their latest update in June (and they wonder why we don't like automated updates).

Starting somewhere between 7.80e33 and 7.81e33, all of the logarithm functions (ln, log, log_y) return 0.

The antilog functions appear to function correctly, as do the various root functions.

The version I have is 11.2605.9.0

I checked the GitHub repository (this app is Open Source) and this bug has been reported.

 

Reminds me of the bug the HP35 first hand-held scientific calculator had.
From Google AI:

 

Collecting antique electronic devices with errors is new to me ... I guess it is akin to finding rare postal stamps with printing errors in them.

 

Collecting antique electronic devices with errors is new to me ... I guess it is akin to finding rare postal stamps with printing errors in them.

As with the stamps, it's not the antiqueness that makes them valuable, but the rarity. Most people that had one of the HP35 calculators that had the error threw it away since they couldn't count on it. Since it was only the very early units that had the bug to begin with, the number of surviving calculators with the bug is rather small, especially since the original market for the calculators was relatively small to begin with. Consider the Pentium chips with the FDIV error. While those have some collector's value, it isn't much because Intel shipped millions of them and many users simply lived with the bug, so CPUs with and without the bug are about equally available.

 

It is not a “bug” but a “feature”.