Bug


My mobile said “sms memory full”. So I did a “delete all”. While my inbox was being emptied, a message came in.  And the inbox was duly emptied. I don’t know who the message was from, even.
Does this happen in your mobile, too? If it doesn’t, what’s the model you’re using?

About wanderlust

just your average books-and-music person who wants to change the world.
This entry was posted in Priya's Travails, Rants. Bookmark the permalink.

8 Responses to Bug

  1. AnSVad says:

    It happened to me too once. My phone was coded in a better way. The messages did not get deleted – all were intact. I had to delete them again after reading the new one that came it. Sony ericsson rocks! 🙂

  2. ya happens says:

    It does happen…..Nokia 1110 …bad mobile

  3. derherr says:

    My mobile stores over 1000 messages so I don’t have to delete all messages very often! that could be a solution to your problem 🙂

    Mine is the Nokia E65, any E series phone can store tons of messages!

  4. rand0mwalker says:

    That tells you how important synchronization is 🙂 . But lot of programmers just ignore that. Good example this one!

  5. wanderlust says:

    @ansvad:
    ah… now that’s a better solution to the problem. it’s still a bug, but atleast you dont miss the message.
    @derherr:
    not necessarily.. what if i just didn’t like a cluttered inbox, or had an sms flamewar and wanted to delete all the messages?
    though, nokia n-series, e-series todally rock.
    @rand0mwalker:
    yasss… that’s what i thought too.
    but is it just too much effort to put in a lock or any other synchronization mechanism, or does it come with a lot of its own problems? or is this too small a problem that a solution like the one on ansvad’s sony ericsson will do for most part?

  6. aNoop says:

    havnt faced it in my motorola too.

  7. rand0mwalker says:

    @wanderlust

    There are multiple solutions to solve synchronization problems like these. Especially when blocking is not an option.
    But the cheapest are:
    a) Abort when unexpected happens. Let the user decide what to do. As in case of ansvad’s phone
    b) don’t care and go ahead with the job at hand. Also known as the Ostrich algorithm. This technique is employed in your phone.

    If you had additional memory to temporarily hold the incoming message while delete is in process, you could have used the double buffering concept, without a lock. But that might be expensive.

    Hey, you asked 😉

  8. wanderlust says:

    yeah, double buffering is an expensive idea. option (a) seems the best.

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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