287193 - crash if I want to move a bookmark while FF is tapped browsing and gives a warning window.

Status: RESOLVED EXPIRED

(Firefox :: Bookmarks & History, defect)

Description

[fruity685-pool]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.6) Gecko/20050226 Firefox/1.0.1 StumbleUpon/1.9993
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.6) Gecko/20050226 Firefox/1.0.1 StumbleUpon/1.9993

the problem arrives when I want to move a bookmark in the bookmark-sidebar from
one place to another, while FF is loading a webpage in a second tab. when FF
dont find the webpage then a warning-window opens ("Warnung: [url] konnte nicht
gefunden werden. Bitte überprüfen Sie den Namen und versuchen Sie es erneut.").
And when I havend finished the bookmarkmove when the warning-window somes, then
FF doesnt respons any instruction. I can close FF only via taskmanager. I
reproduced the problem for 5 times.

Reproducible: Always

Steps to Reproduce:
1. activate the bookmark-sidebar.
2. open the webpage with the url "http://web.psy.herts.ac.uk/" (or every other
webpage that doesnt exist) in a second tab. it is importent that FF need some
time to check that this page doenst exist. (this is essential for this scenario)
3. while FF is trying to load this page achive the following steps.

4. click on a bookmark in the bookmark-sidebar
5. move it into another bookmark-folder or to another place in the
bookmark-list, but (this is importent) dont finish the bookmark-move.
6. hold the mousebutton pressed, so that the bookamrk-move cant be finished.
7. hold in this position until the warning-window arrivs.
8. when the warning-window arrived relinquish the mousebutton (finish the
bookmark move)

Actual Results:  
now FF crashes and dont react to any instruction

Expected Results:  
for me there are two possible ways

a/ FF can finish the bookmark-move and after that FF should show the warning-window.

or

b/ FF should stop the bookmark-move, bring the bookmark to its aboriginal place
and should show the warning window.

I prefer alternative b.

what shoudnt happen is that FF crashes and you lose all opend webpages.

Comment 1

[Adam Hauner]

fruity685-pool: Could you provide Talkback incident ID of your crash?

Comment 2

[fruity685-pool]

(In reply to comment #1)
> fruity685-pool: Could you provide Talkback incident ID of your crash?

[e-mail]: sorry, but I dont know what you mean with incident ID?
Please discribe me how I can get the incident ID.
thanks.

Comment 3

[Robin Monks]

A talkback incident reporting program is included with most official builds of
Firefox.  This program allows you to send information about a crash to Mozilla
when it happens.

The best way to get a report is to download an offical build (or better yet a
nightly build from the "developers" section on mozilla.org) and install it with
talkback.

When you reproduce the bug talkback will open, you can simply enter some
comments and press send.  Now, go to http://talkback-public.mozilla.org and
seach for those comments.  Volia!  Your incident ID with comment will appear.

This report will contain the technical details we need to find and fix the bug.

Comment 4

[Loren Pechtel]

I just hit something like this although I wasn't using the bookmark manager, I
was simply trying to drag it from the menu itself.  Firefox 1.04/XP Home/P4
hyperthreaded.  In my case the bookmark list disappeared when the error box
popped up (English in my case instead of German) and there was no way to
communicate with Firefox other than killing it via the task manager.

Note that this does not appear to generate any error report, the only way out is
a hard kill that won't allow any error reporting functions to run.

If I had to guess the problem lies with the input focus somehow not going to the
modal error box.  I think it's still trying to carry out the drag operation but
that's not possible as you must respond to the box first.

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 7

[Mike Connor [:mconnor]]

sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change