Closed Bug 85294 Opened 24 years ago Closed 24 years ago

Typing in URL bar crashes

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

x86
Linux
defect
Not set
critical

Tracking

()

VERIFIED DUPLICATE of bug 82697

People

(Reporter: guy_hutchison, Assigned: joki)

Details

Attachments

(1 file)

From Bugzilla Helper: User-Agent: Mozilla/4.73 [en] (X11; I; Linux 2.2.15-4mdkfb i686) BuildID: 2001060713 Quickly typing a URL in the nav bar causes a crash. Typing slowly will causes crashes some times but not others. Reproducible: Sometimes Steps to Reproduce: 1. Type new location in URL bar 2. If browser is still running, go to #1 Talkbacks: TB31592959W, TB31592936M, TB31592920Y, TB31592371M, TB31590336Z, TB31590305M, TB31584474W, TB31584414H, TB31583956K
WFM Win98SE 2001061008
Summary: Typing in URL bar crashes → Typing in URL bar crashes
All the stack traces seem to involve just key event junk. CC'ing blizzard because we're crashing in libgdk, reassigning to joki for event stuff Bug ID Trigger Time 2001-06-11 14:36:59 User Comments Trying to go to mozilla.org to file a bug for typing in URLs in location bar Build ID 2001060713 Product ID Netscape6.10B1 Platform ID LinuxIntel Stack Trace libgdk-1.2.so.0 + 0x241c2 (0x402e41c2) libgdk-1.2.so.0 + 0x1448d (0x402d448d) libgdk-1.2.so.0 + 0x143eb (0x402d43eb) handle_key_release_event() dispatch_superwin_event() handle_gdk_event() libgdk-1.2.so.0 + 0x15b80 (0x402d5b80) libglib-1.2.so.0 + 0x10736 (0x40301736) libglib-1.2.so.0 + 0x10d43 (0x40301d43) libglib-1.2.so.0 + 0x10eec (0x40301eec) libgtk-1.2.so.0 + 0x785d9 (0x402565d9) nsAppShell::Run() nsAppShellService::Run() main1() main() libc.so.6 + 0x18cae (0x4040acae)
Assignee: alecf → joki
Component: URL Bar → Event Handling
QA Contact: claudius → gerardok
WFM 2001061108
I can't reproduce this problem. However, there have been changes in that function recently. I don't see anything in the function that should result in a crash, though. I need a better stack trace.
It's very reproducible for me. How would I go about generating a better stack trace?
Fire up the browser in gdb and get a stack trace when it segfaults.
Oh, this is 0.9.1? And do you have your gdk built without log checks? That stack trace shouldn't happen with trunk builds since the gdk_window_put() has been removed because of this problem. See the duplicate bug. I think it's got a similar stack trace and the patch and it's been fixed already. *** This bug has been marked as a duplicate of 82697 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
QA contact updated
QA Contact: gerardok → madhur
v
Status: RESOLVED → VERIFIED
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: