361670 - Assert failure in mozilla/nsprpub/pr/src/misc/prtime.c:1558

Status: RESOLVED DUPLICATE of bug 247896

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Jonas Petersson]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061110 SeaMonkey/1.0.6 Mnenhy/0.7.4.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061110 SeaMonkey/1.0.6 Mnenhy/0.7.4.0

When PR_ParseTimeString() is called with a bad enough string PR_ASSERT on the above line will trigger. Some recent spams with garbage for day/month name will go there. In my case, Seamonkey will exit about 5 min from start (even of left alone) or almost instantly if I try to open the Junk folder. Removing the Junk file helps. I've seen a similar report in Turkish, but could not understand whether it got solved.

Reproducible: Always

Steps to Reproduce:
1. Start seamonkey (select profile if appropriate)
2. Wait 5 minutes
  or
2. Open Junk folder

Special setup: A severely broken Date: line in a junk mail.

Actual Results:  
Assertion failure: tm.tm_month > -1 && tm.tm_mday > 0 && tm.tm_hour > -1 && tm.tm_min > -1 && tm.tm_sec > -1, at ../../../../mozilla/nsprpub/pr/src/misc/prtime.c:1558


Expected Results:  
Not crashed - a broken date is hardly critical. Showing 1/1 1970 is significantly better for instance.

At a glance it seems that setting the default_to_gmt flag might help matters, but I failed to locate where that should be done.

I've flagged it as "Critical", because data is in fact lost (all open windows with forms etc) and once it had happened it made Seamonkey unusable until I located the cause. However, a quick Google seems to indicate that very few users have actually encountered this - or at least they have not told anyone. YMMV.

Comment 1

[Jonas Petersson]

Forgot to mention:
The Turkish issue can be found here:
http://bugs.pardus.org.tr/show_bug.cgi?id=2621

As you can see, this is a Thunderbird user, and the code seems to be common to all  Moz apps so I suspect the problem can occur in a lot of other places too.

Comment 2

[Christian :Biesinger (don't email me, ping me on IRC)]

fixed in thunderbird 2 and later

*** This bug has been marked as a duplicate of 247896 ***