If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Crashes when a large amount of information is copied to the clipboard or when the backspace key is used numerous times in succession.

RESOLVED INCOMPLETE

Status

Core Graveyard
GFX: Gtk
--
critical
RESOLVED INCOMPLETE
12 years ago
9 years ago

People

(Reporter: m074566, Assigned: blizzard)

Tracking

1.7 Branch
Sun
Solaris

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20041221
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20041221

Crashes when a large amount of information is copied to the clipboard or when
the backspace key is used numerous times in succession.

It crashed when trying to copy the above statement to the clipboard by
highlighting it.
Output to terminal caused by fault:

 GLib-CRITICAL **: file gstrfuncs.c: line 186: assertion `string1 != NULL' failed.
Pangolite:Segmentation Fault


    

Reproducible: Always

Steps to Reproduce:
1. Highlight information.
2.
3.

Actual Results:  
Firefox exited and outputted the following to the terminal:

 GLib-CRITICAL **: file gstrfuncs.c: line 186: assertion `string1 != NULL' failed.
Pangolite:Segmentation Fault

Expected Results:  
Highlighted the information and copied it to the clipboard.

Comment 1

12 years ago
Could you test this in a non-ancient build? 

Updated

12 years ago
Assignee: nobody → blizzard
Severity: normal → critical
Component: General → GFX: Gtk
Product: Firefox → Core
QA Contact: general → gtk
Version: unspecified → 1.7 Branch

Comment 2

11 years ago
Can not reproduce it on Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9a5pre) Gecko/20070529 Minefield/3.0a5pre.
  
M074566,Could you please verify the bug again with the latest releases?
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.