Posted by: Bernard Lelchuk | January 2, 2011

First 2011 Bugs hit giants Apple, Google & Microsoft

Dates & Times (E.g. New years eve) bugs are companies’ biggest nightmare – They could affect various features of their products and can cause a negative impact on their clients.
The most famous and “chaotic” bug was Y2K which proved to be exaggerated and caused most companies to rush and spend fortune on software patches in-order to prevent possible failures. 01/01/2000 perceived as ש global blackout – Everyone were alert for the worst possible scenario & employees who worked on that new year’s eve shift earned 100%’s of their regular salary. However, despite all the fuss – In practice only a few systems suffered from this bug and everyone could be relieved.

11 years later, at year 2011 – strange bugs strike us once again – mainly on mobile platforms Apple & Android:

  • Apple’s iPhone devices fail to set-off non-recurring alarm clocks!
  • Google’s Android devices send SMS messages to the WRONG contacts!

Additionally other products were affected:

  • Microsoft’s Hotmail upgrade caused mass email messages & contacts deletion!
  • Remark: The note regarding AVG bugs corresponds the 2011 version of AVG free app which was reported and resolved a few months ago (~ Oct 2010) and not caused by 2011 year bug, therefore removed.
    Thanks Karel for the clarification!

    On another note, year 2011 corresponds to the Year 100 on Taiwan’s Mingou calendar – thus any program which uses 2-digit year values may be affected. According to various posts it seems that the Taiwan government already handled this issue a few years back and so far no issues were reported on this Y1C problem.

These issues make me think strongly on testing coverage & quality as a software testing expert.

Will 2011 continue to hold more ‘surprises’ – I sure hope not. Let’s make 2011 the year of Quality – we can all help in reaching that goal! 🙂

What do you think?

Wish you all a bug-less 2011!

Image: Filomena Scalise /



  1. Hi,
    Your information about ‘Bug 2011 in AVG’ is not correct. If you check your source, this was a bug in one of the early releases of AVG 2011, was fixed very quickly and does not exist in AVG2011 since then. The date of the original post that you quote is October 30 – see
    Let me know if you have any other questions or comments
    Best regards – and a very Happy New Year
    Karel Obluk

    • Thanks Karel for the clarification.
      I’ve removed the AVG bullet and added a remark regarding it.

      Have a great year,

What do YOU think about this post?

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: