Closed
Bug 518382
Opened 15 years ago
Closed 14 years ago
When right clicking in the browser window after copying text from Minq software's DBVisualizer the browser crashes
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: clavalle, Unassigned)
Details
(Keywords: crash, Whiteboard: [CLOSEME 2011-2-15])
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Under Ubuntu ( Linux 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 18:40:08 UTC 2009 i686 GNU/Linux ) when left clicking in the browser window after copying text from Minq software's DBVisualizer the browser crashes.
If I paste the text into a text editor first, copy it from that editor, and right click in the browser window (in anticipation of pasting the text) it does not crash. Ive tested this on Windows (which does not crash) and Ubuntu machines (which all do crash).
Reproducible: Always
Steps to Reproduce:
1.Open Minq Software's DBVisualizer product (v. 6.0.15)
2.Create any kind of text in the SQL Commander
3.Highlight and copy (Ctrl-C) the text
4.Left click anywhere in the Firefox browser window
Actual Results:
Firefox crashes.
Expected Results:
Should have brought up a context menu so I can choose to paste the text.
Comment 1•14 years ago
|
||
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-15]
Comment 2•14 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 4 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•