Intermittent valgrind-test | Invalid write of size 4 at mozilla:: / _pt_root / start_thread / clone

REOPENED
Unassigned

Status

()

Core
General
P3
normal
REOPENED
2 years ago
2 days ago

People

(Reporter: Treeherder Bug Filer, Unassigned, NeedInfo)

Tracking

({bulk-close-intermittents, intermittent-failure})

unspecified
bulk-close-intermittents, intermittent-failure
Points:
---

Firefox Tracking Flags

(firefox50 affected, firefox51 affected, firefox52 wontfix)

Details

(Whiteboard: [ele:1b])

Attachments

(1 obsolete attachment)

Comment hidden (mozreview-request)

Updated

2 years ago
Attachment #8783427 - Attachment is obsolete: true

Comment 3

2 years ago
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3

Comment 4

a year ago
6 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 3
* try: 1
* fx-team: 1
* autoland: 1

Platform breakdown:
* linux64: 6

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1296819&startday=2016-09-19&endday=2016-09-25&tree=all
Am I reading the stack right that this looks like an issue with the hang monitor?
status-firefox50: --- → affected
status-firefox51: --- → affected
status-firefox52: --- → affected
Flags: needinfo?(jseward)
(In reply to Ryan VanderMeulen [:RyanVM] from comment #5)
> Am I reading the stack right that this looks like an issue with the hang
> monitor?

Well, I don't know if it is an issue with the hang monitor per se.
The invalid write to 0x0 is this, at the end of "void RunWatchdog(void* arg)"
(the watchdog thread main function):

    // Shutdown is apparently dead. Crash the process.
    MOZ_CRASH("Shutdown too long, probably frozen, causing a crash.");

So the question that comes to mind is: why is this timing out now when it
didn't previously?
Flags: needinfo?(jseward)

Comment 7

a year ago
5 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* autoland: 3
* mozilla-inbound: 1
* mozilla-central: 1

Platform breakdown:
* linux64: 5

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1296819&startday=2016-10-03&endday=2016-10-09&tree=all

Comment 8

a year ago
9 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* autoland: 4
* mozilla-inbound: 3
* mozilla-aurora: 2

Platform breakdown:
* linux64: 9

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1296819&startday=2016-10-17&endday=2016-10-23&tree=all

Comment 9

a year ago
16 automation job failures were associated with this bug in the last 7 days.

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

Platform breakdown:
* linux64: 16

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1296819&startday=2016-10-24&endday=2016-10-30&tree=all
11 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 6
* autoland: 5

Platform breakdown:
* linux64: 11

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1296819&startday=2016-10-31&endday=2016-11-06&tree=all
6 failures in 749 pushes (0.008 failures/push) were associated with this bug in the last 7 days.  

Repository breakdown:
* mozilla-inbound: 5
* mozilla-aurora: 1

Platform breakdown:
* linux64: 6

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1296819&startday=2017-01-23&endday=2017-01-29&tree=all
Mass wontfix for bugs affecting firefox 52.
status-firefox52: affected → wontfix
Hello, I'm asking your help with an experiment with making decisions on bugs. You've been needinfo'ed on this bug. I'd like you to take one action to help this bug make progress toward a decision. The things you can do include:

* If you know or have a good guess of which product and component this bug belongs to, change the product and component of the bug
* If you know of the right person to ask about this bug, redirect the needinfo to them
* If you cannot reproduce the bug, close it

All we need you to do is one thing that will help us make a decision on the bug or resolve it.

Thank you for your help with this. If you have questions, please contact emma@mozilla.com.
Flags: needinfo?(valentin.gosu)
Whiteboard: [ele:1b]
Flags: needinfo?(valentin.gosu) → needinfo?(hchang)
Not sure why I am ni'ed but I am trying to give feedback as far as I know:

1) There seems to be a wrong review commit (from me) pushed to this bug but it shouldn't
   be relevant to this bug.

2) I didn't find the stack but that reminds me a safebrowsing "long hang crash" which
   has been resolved for a while.
Flags: needinfo?(hchang)
Thanks for that. It also seemed to me that this hasn't been reproduced in a while, but I thought I would ask someone who looked at it previously. Seems I should have looked more carefully.

Closing as WORKSFORME
Status: NEW → RESOLVED
Last Resolved: 9 months ago
Resolution: --- → WORKSFORME

Comment 17

6 months ago
1 failures in 949 pushes (0.001 failures/push) were associated with this bug in the last 7 days.   

Repository breakdown:
* mozilla-inbound: 1

Platform breakdown:
* linux64: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1296819&startday=2017-08-14&endday=2017-08-20&tree=all
Status: REOPENED → RESOLVED
Last Resolved: 9 months ago6 months ago
Keywords: bulk-close-intermittents
Resolution: --- → INCOMPLETE

Comment 18

5 months ago
1 failures in 885 pushes (0.001 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* autoland: 1

Platform breakdown:
* linux64: 1

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

Comment 19

5 months ago
1 failures in 824 pushes (0.001 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 1

Platform breakdown:
* linux64: 1

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

Updated

11 days ago
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
25 failures in 685 pushes (0.036 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 13
* autoland: 10
* mozilla-central: 2

Platform breakdown:
* linux64: 25

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1296819&startday=2018-02-12&endday=2018-02-18&tree=all
This has become a frequent failure. First failure after a long break was on 2018-02-14.

Julian, can you take a look at this or redirect to an appropriate contact, please?
Flags: needinfo?(jseward)
15 failures in 151 pushes (0.099 failures/push) were associated with this bug yesterday.    

Repository breakdown:
* autoland: 13
* mozilla-inbound: 2

Platform breakdown:
* linux64: 15

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1296819&startday=2018-02-22&endday=2018-02-22&tree=all
18 failures in 135 pushes (0.133 failures/push) were associated with this bug yesterday.    

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

Platform breakdown:
* linux64: 18

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1296819&startday=2018-02-23&endday=2018-02-23&tree=all
You need to log in before you can comment on or make changes to this bug.