Closed
Bug 304164
Opened 19 years ago
Closed 19 years ago
Crash if date in distant future is selected from the "Go To Date" dialog
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 278236
People
(Reporter: seanh, Assigned: mostafah)
References
Details
(Keywords: crash)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050809 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050809 Mozilla Sunbird/0.2+
If from the Go To Date Dialog a date such as 10/08/2050 is selected Sunbird Crashes.
Reproducible: Always
Steps to Reproduce:
1.Select Go To Date Dialog
2.Insert a date about 50 years ahead (or to be safe a thousand years)
3.Press the Ok Button
Actual Results:
Mozilla Sunbird crashes
Expected Results:
A dialog should appear indicating that the date is too far in the future.
Comment 1•19 years ago
|
||
Confirming on.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050809 Mozilla
Sunbird/0.2+
No error in debug-console.
This appear in JS-console at startup though(I don't think it's related, but anyway):
Error: MidnightSelectedDate is not defined
Source File: chrome://calendar/content/unifinder.js
Line: 658
Summary: Crash if date in distant future is selected from the "Go To Date" dialog → Crash if date in distant future is selected from the "Go To Date" dialog
Comment 2•19 years ago
|
||
Works for me on Linux, but fails WinXP, so this seems to be Windows only. A
couple extra tests I'd like to see:
1.) Set your system's date to something very far in the future. Then start
Sunbird. It should show that date on startup.
2.) Any chance of getting a maxdate you can go to without crashing? (I think I
remember something special about 2037/2038 or so.)
Status: NEW
Blocks 0.3a1, but not severely. (That is, if this is the only bug left, I vote
for shipping anyway.)
Reporter | ||
Comment 3•19 years ago
|
||
I can get to 2037 without crashing, after that it crashes. But on a more
important note, I set my clock (in Windows XP) to 2050, then tried to test this
bug. I couldn't get Sunbird to start without crashing.
Comment 4•19 years ago
|
||
(In reply to comment #3)
> I can get to 2037 without crashing, after that it crashes. But on a more
> important note, I set my clock (in Windows XP) to 2050, then tried to test this
> bug. I couldn't get Sunbird to start without crashing.
Thanks. This is good to know. 2 new tests:
1.) Open the javascript console. Type "var d = new Date(2075,1,1); d;" without
the quotes and click 'Evaluate'. Does this crash or give errors or work normally?
2.) Go to 2037 and try paging forward using the arrows in the views until you
get to a date you normally crash. Can you?
Reporter | ||
Comment 5•19 years ago
|
||
1.) Open the javascript console. Type "var d = new Date(2075,1,1); d;" without
the quotes and click 'Evaluate'. Does this crash or give errors or work normally?
This works fine
2.) Go to 2037 and try paging forward using the arrows in the views until you
get to a date you normally crash. Can you?
Paging forward causes a crash as soon as I reach January 2038.
Comment 6•19 years ago
|
||
I stumbled on bug 278236 accidentally, which covers this. Thanks for the help
in testing this, though. Resolving as a duplicate.
*** This bug has been marked as a duplicate of 278236 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Updated•19 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•