Closed Bug 303771 Opened 19 years ago Closed 19 years ago

Changing progress with right-click crashes sunbird.

Categories

(Calendar :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: robin.edrenius, Assigned: mostafah)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050806 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050806 Firefox/1.0+

Right-clicking on a task and changing events first to 50% then to 25% crashes
sunbird.

Reproducible: Always

Steps to Reproduce:
1. Right click in task-field -> create a new event
2. Right click on the new event -> progress -> 50%
3. Right click on the new event -> progress -> 25%

Actual Results:  
Sunbird crashes and the standard XP crash message appear:
"sunbird.exe has encountered a problem and needs to close.  We are sorry for the
inconvenience."

Expected Results:  
Changed the progress to 25%
Version: unspecified → Trunk
Robin,
    Thanks for the bug report.  Right now I'm unable to reproduce this.  Can you
think of anything additional that might help track this down?  After setting the
percent complete to 50%, are there any errors in the JavaScript console?  Also,
I doubt it will help, but please also include your version information from
Help-> About.  Finally, can you confirm that you intended to choose
'Reproducable: Always'?
Works for me on Windows 2000 with a current nightly. Could you try it again with
a fresh profile and could you tell us which version of Sunbird you are using?
Version: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4)
Gecko/20050806 Mozilla Sunbird/0.2+

Sometimes the crash occurs only by setting the progress to 50%.
No errors occour when setting the progress to 50%.

I'm not sure what else to tell you, tell me what kind of information you need
and I'll give it to you.

Tried with new profile, the crash still occur
(In reply to comment #3)
> Sometimes the crash occurs only by setting the progress to 50%.
> No errors occour when setting the progress to 50%.

I may have been a bit unclear there, I meant to say that no error occur in the
javascript console when setting the progress to 50% (I don't know how to check
for such errors when the application crashes though)
Robin,
  Can you please download a nightly from 18 July?
http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/2005-07-18-07-trunk/

You may need to download an extra dll file to run this, as described here:
http://forums.mozillazine.org/viewtopic.php?t=291076
Running this build will open a console that will display much more information
about what is going on in the background of the program.  First, confirm that
the behavior is still reproducable then.  Then, if/when Sunbird crashes, please
copy the output from the terminal into a text document (use notepad/wordpad) and
attach it to this bug.

If it isn't reproducable in the 18 July nightly, then I have to ask you to do
the unenviable task of trying to narrow down where the problem cropped up.  Here
is a list of all the recent nightlies:
http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/
It would be really useful if you could say the last build that works and the
first that doesn't.

Thanks.
Wait, I forgot, if Sunbird crashes, the console will probably close, unless you
opened it yourself.  Therefore, please try this with the 6 Aug nightly: Open a
command prompt. (Start->Accessories->Command prompt) Then run Sunbird from in
there.  You should type something like c:\<path to Sunbird
directory>\sunbird\sunbird.exe where <path to Sunbird directory> is wherever you
unzipped the nightly build to.  This should give you more information about the
crash.

THEN, try it also in the 18 July nightly.
(In reply to comment #6)
> Wait, I forgot, if Sunbird crashes, the console will probably close, unless you
> opened it yourself.  Therefore, please try this with the 6 Aug nightly: Open a
> command prompt. (Start->Accessories->Command prompt) Then run Sunbird from in
> there.  You should type something like c:\<path to Sunbird
> directory>\sunbird\sunbird.exe where <path to Sunbird directory> is wherever you
> unzipped the nightly build to.  This should give you more information about the
> crash.
> 
> THEN, try it also in the 18 July nightly.

I'm terrbily sorry, but I'm not sure what information that's supposed to give me.

If I'm supposed to run the 6 aug nightly with the -console switch, the only info
that gives me is:

Starting calendar alarm service
error creating table cal_calendars -- probably already exists
error creating table cal_calendars_prefs -- probably already exists
*** Calendar schema version is: 4
*** Calendar schema version is: 4
observer added

And that is when it's starting, after/during the crash it doesn't give any
information.
I'm very sorry if I'm overlooking something very simple here, but you must
consider that this is my first bug-report. =)
(In reply to comment #7)
> Starting calendar alarm service
> error creating table cal_calendars -- probably already exists
> error creating table cal_calendars_prefs -- probably already exists
> *** Calendar schema version is: 4
> *** Calendar schema version is: 4
> observer added
> 
> And that is when it's starting, after/during the crash it doesn't give any
> information.
> I'm very sorry if I'm overlooking something very simple here, but you must
> consider that this is my first bug-report. =)
> 

That's exactly what I wanted.  Sometimes if the backend database fails, it will
report an error in the console.  Can you do the same with the 18 July nightly?

And don't apologize, you're much more helpful than most of our bug reports :-) 
Finally, if you have access to IRC, you can come on to #calendar in
irc.mozilla.org, which will save everyone the bug mail.  Later, I'll come back
here and comment the relevant details for everyone to see.

Additional info from IRC: The crash alert reads "Faulting application
sunbird.exe, version 0.2.0.0, faulting module xpcom_core.dll, version
1.8.20050.15071, fault address 0x0002d089."

The crash happens before contextChangeProgress() in unifinderToDo.js is reached.
 Reporter says it is reproducable always for changing 50%->25% and 75%->50%,
most of the time for changes involving 0% or 100%.
Looks like this have been fixed! Works for me on Mozilla/5.0 (Windows; U;
Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050920 Mozilla Sunbird/0.2+

Resolving as worksforme.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.