The default bug view has changed. See this FAQ.

Continued typing after a failed search hangs application

RESOLVED FIXED in mozilla1.9.2a1

Status

()

Toolkit
Places
RESOLVED FIXED
8 years ago
8 years ago

People

(Reporter: sdwilsh, Unassigned)

Tracking

Trunk
mozilla1.9.2a1
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

8 years ago
If you continue to type after a failed search in the location bar (no results), the application will hang.

It's not clear why this is doing this yet.  I am a bit concerned that we may be trying to do some synchronous query that has to wait until the asynchronous one is completed.  This needs investigation.
(Reporter)

Comment 1

8 years ago
If somebody wants to jump in and help here - getting a profile of the main thread during the hang would be incredibly useful.
(Reporter)

Comment 2

8 years ago
And if you do want to take me up on comment 1, sharkable builds can be found at http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-places/
Blocks: 455555
No longer depends on: 455555
(Reporter)

Comment 3

8 years ago
It would seem that the issue here is lock contention.  The background thread in storage keeps grabbing the mutex for the database handle, and each call to executeAsync will need the lock as well.  We can partially work around this to some degree, but for a real, good fix, we'd need to have SQLite architectural changes here.  This does put bug 455555 at risk for making 3.6 I think.
(Reporter)

Updated

8 years ago
Depends on: 505550
(Reporter)

Updated

8 years ago
Depends on: 505813
(Reporter)

Updated

8 years ago
Depends on: 505871
(Reporter)

Updated

8 years ago
Depends on: 506023
(Reporter)

Updated

8 years ago
No longer depends on: 505550
(Reporter)

Updated

8 years ago
No longer depends on: 506023
(Reporter)

Updated

8 years ago
Depends on: 506022
(Reporter)

Updated

8 years ago
(Reporter)

Updated

8 years ago
Depends on: 506805
(Reporter)

Updated

8 years ago
(Reporter)

Comment 4

8 years ago
Neglected to close this when dependent bugs were fixed.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.