Open Bug 375674 Opened 17 years ago Updated 2 years ago

"Already running" error dialog should tell user what URL was requested (if any)

Categories

(Firefox :: General, enhancement)

x86
Linux
enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: site-mozilla-bugzilla, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20060601 Firefox/2.0.0.2 (Ubuntu-edgy)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20060601 Firefox/2.0.0.2 (Ubuntu-edgy)

Let's say I'm using my standalone feed reader (LiFeRea, in this case, but doesn't matter) and click on a bunch of items, expecting them to open in the existing Firefox window.  If my system is laggy, I might click a number of links very quickly, and a number of seconds after I've marked those as read and moved on to other feed items, I get the dreaded message:

"Firefox is already running, but is not responding. To open a new window, you
must first close the existing Firefox process, or restart your system."

Sometimes several of these will appear. Now, since viewing a feed item marks it as read, I don't know for which items I've clicked "Read More" and not received an open tab.

The dialog box should *at least* display the URL that was requested (if any), even *better* could display it as copy-able text, and *ideally* would offer to retry the URL.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Severity: minor → enhancement
This is a mass search for bugs that are in the Firefox General component, are
UNCO, and have not been changed for 800 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10, create a fresh profile,
http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you
still see the bug, please update this bug. If the issue is gone, please set the
resolution to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
Whiteboard: [CLOSEME 2010-11-01]
I cannot reliably reproduce the dialog box, but the last time I saw it, it still had this problem.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.