Open
Bug 469667
Opened 16 years ago
Updated 6 months ago
Browser stops loading if no events happen in system (n810 hardware)
Categories
(Core :: XPCOM, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: starkov.egor, Unassigned)
References
Details
Attachments
(1 file)
2.45 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4 Build Identifier: Browser stalls until any event happen in system. It happens because mayWait flag is TRUE in nsAppShell::ProcessNextNativeEvent and core goes to idle loop. Backtrace is in attachment. mayWait flag is FALSE in nsThread::ProcessNextEvent but after it is lost and not handled, so it becomes TRUE. It happens because mayWait is not passed as parameter and default parameter is used. Reproducible: Sometimes Steps to Reproduce: 1. open browser 2. type 'g' in address bar 3. press enter Actual Results: broser stalls sometimes and continues loading after some events like clicking Expected Results: browser should load page immediately
Reporter | ||
Comment 1•16 years ago
|
||
Updated•16 years ago
|
Attachment #353026 -
Attachment mime type: text/x-log → text/plain
Reporter | ||
Updated•16 years ago
|
Depends on: nsIThreadManager
Comment 2•16 years ago
|
||
Here is the GTK workaround for this problem. https://garage.maemo.org/svn/browser/mozilla/trunk/microb-engine/microb-engine/debian/patches/not_sorted/92422.workaround.diff We are pushing event into queue if there are no any events and myWait = 1.
Updated•2 years ago
|
Severity: normal → S3
Comment hidden (spam) |
You need to log in
before you can comment on or make changes to this bug.
Description
•