Open
Bug 1278917
Opened 9 years ago
Updated 1 year ago
Execution of atomic javascript function gots interrupted by an onload callback eventhandler
Categories
(Core :: DOM: Core & HTML, defect, P2)
Core
DOM: Core & HTML
Tracking
()
UNCONFIRMED
People
(Reporter: jsrosman, Unassigned)
References
()
Details
(Keywords: parity-chrome, parity-edge, Whiteboard: btpp-followup-2016-06-15,domcore-bugbash-triaged)
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36
Steps to reproduce:
- place attached file race.htm on website and open it in browser
- you can also try this link https://jsfiddle.net/34oubfeq/
Actual results:
In Firefox the webpage shows: ERROR: RACE Condition!!!!!
Expected results:
2 alerts with "OK" should appear and Webpage should show "OK"
Severity: normal → critical
OS: Unspecified → All
Priority: -- → P1
Hardware: Unspecified → All
Summary: Execution of atomic javascript function gots interrupted by a callback eventhandler of an async operation → Execution of atomic javascript function gots interrupted by an onload callback eventhandler
Comment 1•9 years ago
|
||
This is a dup of the bug that we spin event loop during alert
Component: DOM: Events → DOM
It also happens when we do a sync XHR in stead of an alert (See commented code in the example)
Having same issue with chrome on linux:
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.37 Safari/537.36
Comment 4•9 years ago
|
||
(In reply to Olli Pettay [:smaug] (high review load, please consider other reviewers) from comment #1)
> This is a dup of the bug that we spin event loop during alert
Bug 1173716?
Whiteboard: btpp-followup-2016-06-15
Sorry, wrong browser used for lookup of user agent. I had same issue with Firefox on linux (so with chrome it is working fine): Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Updated•9 years ago
|
Whiteboard: btpp-followup-2016-06-15 → btpp-followup-2016-06-15[parity-Chrome][parity-Edge]
(In reply to Andrew Overholt [:overholt] from comment #4)
> (In reply to Olli Pettay [:smaug] (high review load, please consider other
> reviewers) from comment #1)
> > This is a dup of the bug that we spin event loop during alert
>
> Bug 1173716?
This is not a duplicate but I think it is related. I have attached a new reproduction scenario (race_case2.htm) where we load 2 iframes while doing a synchroneous XmlHttpRequest. Same issue in FF. This can also be reproduced with window.open().
Comment 8•9 years ago
|
||
Hi All,
Please fix this. This is a fundamental break in the functionality.
Updated•8 years ago
|
Priority: -- → P2
Comment 9•7 years ago
|
||
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome,
parity-edge
Whiteboard: btpp-followup-2016-06-15[parity-Chrome][parity-Edge] → btpp-followup-2016-06-15
| Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•3 years ago
|
Severity: normal → S3
Comment 13•2 years ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:edgar, since the bug has recent activity, could you have a look please?
For more information, please visit BugBot documentation.
Flags: needinfo?(jsrosman) → needinfo?(echen)
Comment 14•2 years ago
|
||
There are some details in https://bugzilla.mozilla.org/show_bug.cgi?id=1173716#c20.
Comment 16•1 year ago
|
||
[domcore-bugbash-triaged] Doing domcore random bug triage - this is still valid.
Whiteboard: btpp-followup-2016-06-15 → btpp-followup-2016-06-15,domcore-bugbash-triaged
Comment 18•1 year ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:masayuki, since the bug has recent activity, could you have a look please?
For more information, please visit BugBot documentation.
Flags: needinfo?(pazzzz123456) → needinfo?(masayuki)
It was requested by the spam comment self.
Flags: needinfo?(masayuki)
You need to log in
before you can comment on or make changes to this bug.
Description
•