Closed Bug 212252 Opened 22 years ago Closed 19 years ago

dragging a selection causes reproducible lockup

Categories

(Core :: DOM: Selection, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: pde-lists, Assigned: mjudge)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030704 Debian/1.4-1 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030704 Debian/1.4-1 I have had this problem periodically from at least 1.2 through to 1.4: When I select a piece of text, and then drag it, I occasionally see the cursor change to an "inverted L" shape, locking X in the process. Switching to a console and killing mozilla-bin is the only way to recover. This is observable with debian and with mozilla.org binaries, and does not seem to be a duplicate of the "popup dialogues during selection cause crashes" bug. Reproducible: Always Steps to Reproduce: 1.Select a few words/lines of text 2."drag" the text randomly with the left mouse button 3.repeat til lockup - this sometimes takes a minute or two Actual Results: The cursor becomes stuck in "inverted L" drag and drop form, and X locks up. Recovery is only possible by killing mozilla-bin from the console Expected Results: Not locked up :) Strace available at http://www.cs.mu.oz.au/~pde/bugs/mozilla.strace.gz Some further details are available at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=180425
try: 1. waiting a really long time 2. hitting "Esc"
I tried that (waiting a few minutes, pressing escape) -- no luck
I also just observed this behvaiour in Firebird 0.6 (using debian's 0.6-8 packages). I'm not sure how to tag this bug as existing in Firebird, without moving it to firebird...
> I'm not sure how to tag this bug as existing in Firebird... most of the relevant code is shared, so that's to be expected.
Two questions: 1. Is this a gtk 1.2 build or a gtk2 build? 2. Do you see it in the 1.4 final build?
I'm currently seeing the bug with GTK2 builds (Debian's mozilla-browser 2:1.4-2, library versions shown below); I'm pretty sure the upstream version I reproduced it in was 1.4 final. I've also seen it in older GTK1.2 builds (such as 1.2.1-9, which it's reported against in Debian's bug tracking system). Versions of the packages mozilla-browser depends on: ii debconf 1.2.27 Debian configuration management system ii libatk1.0-0 1.2.4-1 The ATK accessibility toolkit ii libc6 2.3.1-16 GNU C Library: Shared libraries and Timezone ii libgcc1 3.3.1-0pre0 GCC support library ii libglib2.0-0 2.2.2-1 The GLib library of C routines ii libgtk2.0-0 2.2.1-2 The GTK+ graphical user interface library ii libnspr4 1.4-2 Netscape Portable Runtime Library ii libpango1.0-0 1.2.1-1 Layout and rendering of internationalized te ii libstdc++5 3.3.1-0pre0 The GNU Standard C++ Library v3 ii psmisc 20.2-2.1 Utilities that use the proc filesystem ii xlibs 4.2.1-5 X Window System client libraries ii zlib1g 1.1.4-1 compression library - runtime
I haven't been able to reproduce this bug in mozilla for a while, which is a bit odd. But I did just see it in gaim, which presumably confirms that it's somewhere in gtk (or another library). For cross-referential purposes: Versions of the packages gaim (1:0.67-3) depends on: ii libao2 0.8.3-1 Cross Platform Audio Output Library ii libaspell15 0.50.3-5 The GNU Aspell spell-checker runtime toolkit ii libatk1.0-0 1.2.4-1 The ATK accessibility toolkit ii libaudiofile0 0.2.3-4 The Audiofile Library ii libc6 2.3.2-2 GNU C Library: Shared libraries and Timezone ii libglib2.0-0 2.2.2-1 The GLib library of C routines ii libgtk2.0-0 2.2.1-2 The GTK+ graphical user interface library ii libgtkspell0 2.0.4-5 a spell-checking addon for GTK's TextView wi ii libpango1.0-0 1.2.1-1 Layout and rendering of internationalized te ii libperl5.8 5.8.0-13 Shared Perl library. ii xlibs 4.2.1-5 X Window System client libraries
I can't reproduce with debian's: mozilla-browser_1.7.3-5 libgtk2.0-0_2.4.14-2 Please confirm this bug or close it.
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.