1336630 - Intermittent dom/promise/tests/test_promise.html | application crashed [@ js::CompartmentChecker::check] after Assertion failure: IsInsideNursery(obj) || !obj->asTenured().isMarked(gc::GRAY), at /home/worker/workspace/build/src/js/src/jscntxtinlines.h:71

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Description

[Treeherder Bug Filer]

Filed by: wkocher [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=74424484&repo=autoland

https://queue.taskcluster.net/v1/task/Kr7x339aT0mTCf93i4cwDQ/runs/0/artifacts/public/logs/live_backing.log

Comment 1

[Intermittent Failures Robot]

5 failures in 733 pushes (0.007 failures/push) were associated with this bug in the last 7 days.  

Repository breakdown:
* mozilla-inbound: 2
* try: 1
* mozilla-central: 1
* autoland: 1

Platform breakdown:
* linux32: 3
* linux64: 2

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-01-30&endday=2017-02-05&tree=all

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

it looks like there is a lot of action in bug 1292852, possibly we wait until that bug is resolved before looking more into this?

this is happening right after:  dom/promise/tests/test_promise.html

I also did some retriggers that might help point out if a specific patch triggered this:
https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=debug%20mochitest-5%20linux&tochange=711aa14e4c4cfe5a39fd3c06ac67c4bb31573375&fromchange=f49a72bc7aed912d7cbb546ac5bab19f46b38969&selectedJob=74396057

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

ok, the main tracking bug is bug 1317672.

Comment 4

[Intermittent Failures Robot]

22 failures in 153 pushes (0.144 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* mozilla-inbound: 9
* autoland: 9
* mozilla-central: 4

Platform breakdown:
* linux32: 12
* linux64: 10

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-09&endday=2017-02-09&tree=all

Comment 5

[Intermittent Failures Robot]

38 failures in 152 pushes (0.25 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* mozilla-inbound: 20
* autoland: 17
* graphics: 1

Platform breakdown:
* linux64: 20
* linux32: 18

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-10&endday=2017-02-10&tree=all

Comment 6

[Intermittent Failures Robot]

164 failures in 836 pushes (0.196 failures/push) were associated with this bug in the last 7 days. 

This is the #8 most frequent failure this week. 

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **

Repository breakdown:
* mozilla-inbound: 79
* autoland: 68
* mozilla-central: 10
* try: 5
* graphics: 2

Platform breakdown:
* linux64: 92
* linux32: 72

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-06&endday=2017-02-12&tree=all

Comment 7

[Intermittent Failures Robot]

26 failures in 114 pushes (0.228 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* mozilla-inbound: 12
* autoland: 10
* try: 2
* mozilla-central: 2

Platform breakdown:
* linux64: 18
* linux32: 8

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-13&endday=2017-02-13&tree=all

Comment 8

[Intermittent Failures Robot]

33 failures in 161 pushes (0.205 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* mozilla-inbound: 15
* autoland: 11
* graphics: 6
* mozilla-central: 1

Platform breakdown:
* linux64: 19
* linux32: 13
* windows8-64: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-14&endday=2017-02-14&tree=all

Comment 9

[Intermittent Failures Robot]

24 failures in 143 pushes (0.168 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* mozilla-inbound: 12
* autoland: 10
* try: 1
* mozilla-central: 1

Platform breakdown:
* linux64: 14
* linux32: 10

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-15&endday=2017-02-15&tree=all

Comment 10

[Intermittent Failures Robot]

34 failures in 151 pushes (0.225 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* autoland: 17
* mozilla-inbound: 14
* mozilla-central: 3

Platform breakdown:
* linux64: 17
* linux32: 17

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-16&endday=2017-02-16&tree=all

Comment 11

[Intermittent Failures Robot]

41 failures in 180 pushes (0.228 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* autoland: 20
* mozilla-inbound: 15
* mozilla-central: 3
* graphics: 2
* try: 1

Platform breakdown:
* linux32: 26
* linux64: 15

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-17&endday=2017-02-17&tree=all

Comment 12

[Intermittent Failures Robot]

168 failures in 833 pushes (0.202 failures/push) were associated with this bug in the last 7 days. 

This is the #11 most frequent failure this week. 

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **

Repository breakdown:
* mozilla-inbound: 74
* autoland: 70
* mozilla-central: 11
* graphics: 8
* try: 5

Platform breakdown:
* linux64: 86
* linux32: 81
* windows8-64: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-13&endday=2017-02-19&tree=all

Comment 13

[Intermittent Failures Robot]

16 failures in 141 pushes (0.113 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* autoland: 10
* mozilla-inbound: 2
* mozilla-central: 2
* graphics: 2

Platform breakdown:
* linux32: 10
* linux64: 6

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-21&endday=2017-02-21&tree=all

Comment 14

[Intermittent Failures Robot]

18 failures in 173 pushes (0.104 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* mozilla-inbound: 8
* autoland: 5
* mozilla-central: 4
* graphics: 1

Platform breakdown:
* linux64: 11
* linux32: 7

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-22&endday=2017-02-22&tree=all

Comment 15

[Joel Maher ( :jmaher ) (UTC -8)]

waiting on action in bug 1317672

Comment 16

[Intermittent Failures Robot]

15 failures in 182 pushes (0.082 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* autoland: 6
* mozilla-inbound: 5
* mozilla-central: 2
* graphics: 2

Platform breakdown:
* linux64: 10
* linux32: 5

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-24&endday=2017-02-24&tree=all

Comment 17

[Intermittent Failures Robot]

91 failures in 812 pushes (0.112 failures/push) were associated with this bug in the last 7 days. 

This is the #16 most frequent failure this week. 

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **

Repository breakdown:
* autoland: 41
* mozilla-inbound: 33
* graphics: 9
* mozilla-central: 8

Platform breakdown:
* linux64: 47
* linux32: 44

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-20&endday=2017-02-26&tree=all

Comment 18

[Intermittent Failures Robot]

16 failures in 125 pushes (0.128 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* autoland: 9
* mozilla-inbound: 5
* try: 1
* graphics: 1

Platform breakdown:
* linux32: 10
* linux64: 6

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-27&endday=2017-02-27&tree=all

Comment 19

[Jon Coppeard (:jonco)]

I've run this test (and dom/promise/tests) locally 1000 times in a loop and haven't seen any failures.

Comment 20

[Joel Maher ( :jmaher ) (UTC -8)]

this fails on linux32/64 debug, specifically in e10s.  Are you running that config?

Comment 21

[Jon Coppeard (:jonco)]

(In reply to Joel Maher ( :jmaher) from comment #20)
Yes, linux64 optdebug build with e10s.

Comment 22

[Joel Maher ( :jmaher ) (UTC -8)]

trying a random idea- we run these browser-chrome tests on ubuntu 12.04, what if we run on 16.04... :)

https://treeherder.mozilla.org/#/jobs?repo=try&author=[e-mail]&filter-searchStr=browser-chrome&group_state=expanded&fromchange=9bb14b87c3306c0b91cfc1ab336ea37585fb93f0

Comment 23

[Joel Maher ( :jmaher ) (UTC -8)]

bummer, similar rates of failure on 12.04 vs 16.04;

:jonco, possibly you could reproduce/debug using a 1 click loaner.

Comment 24

[Intermittent Failures Robot]

18 failures in 181 pushes (0.099 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* mozilla-inbound: 8
* autoland: 5
* try: 2
* graphics: 2
* mozilla-central: 1

Platform breakdown:
* linux64: 10
* linux32: 8

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-03-01&endday=2017-03-01&tree=all

Comment 25

[Joel Maher ( :jmaher ) (UTC -8)]

the question is why does this specific test dom/promise/tests/test_promise.html cause the gc:GRAY assertion?  

With the troubles to reproduce this locally, I am planning on disabling this one specific test for linux/debug later this week.

Comment 26

[Intermittent Failures Robot]

18 failures in 149 pushes (0.121 failures/push) were associated with this bug yesterday.  
Repository breakdown:
* try: 4
* graphics: 4
* autoland: 4
* mozilla-inbound: 3
* mozilla-central: 2
* oak: 1

Platform breakdown:
* linux64: 9
* linux32: 9

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-03-02&endday=2017-03-02&tree=all

Comment 27

[Jon Coppeard (:jonco)]

(In reply to Joel Maher ( :jmaher) from comment #25)
> the question is why does this specific test
> dom/promise/tests/test_promise.html cause the gc:GRAY assertion?  

I've had a look at the promises implementation and couldn't find anything wrong with it that would cause this.  What's probably happening is that the gray marking state for some object is wrong and we're only finding out when it's touched by the promises code at a later time.

Problems like this can be sensitive and non-deterministic, for example depending on the timing incremental GC slices.

> With the troubles to reproduce this locally, I am planning on disabling this
> one specific test for linux/debug later this week.

Could you leave it enabled at least until mid-next week?  I've got a couple more patches to land that may affect things, and we won't know whether it's fixed if the test is disabled.

Comment 28

[Joel Maher ( :jmaher ) (UTC -8)]

yeah, I can do that.  Would it help to reduce the test case to what is causing the assertions?  I could push a series of them to try to help out- not sure if that would help, but happy to do it.

Comment 29

[Intermittent Failures Robot]

77 failures in 783 pushes (0.098 failures/push) were associated with this bug in the last 7 days. 

This is the #13 most frequent failure this week. 

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **

Repository breakdown:
* autoland: 36
* mozilla-inbound: 19
* try: 9
* graphics: 9
* mozilla-central: 3
* oak: 1

Platform breakdown:
* linux32: 42
* linux64: 35

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1336630&startday=2017-02-27&endday=2017-03-05&tree=all

Comment 30

[Joel Maher ( :jmaher ) (UTC -8)]

this looks to be fixed around March 5th :)

Comment 31

[Ryan VanderMeulen [:RyanVM]]

Bug 1342181 would be believable I'd think.