Closed Bug 1375912 Opened 7 years ago Closed 7 years ago

Crash in mozilla::a11y::LazyInstantiator::AccumulateTelemetry

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Platform:
Unspecified
Windows
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1375412

People

(Reporter: bugzilla, Assigned: bugzilla)

Details

(Keywords: crash, regression)

(In reply to Ryan VanderMeulen [:RyanVM]) > Users on today's nightly are still crashing :( > https://crash-stats.mozilla.com/report/index/076e9b6d-8158-4b97-8dd4-c64800170623
See Also: → 1375130
Crash Signature: mozilla::a11y::LazyInstantiator::AccumulateTelemetry] → mozilla::a11y::LazyInstantiator::AccumulateTelemetry] [@ nsCOMPtr_base::assign_assuming_AddRef | mozilla::detail::RunnableMethodImpl<T>::Run ]
The aforementioned crash report is mine. I submitted a few dozen crash reports today. :) If you'd like to reach me for anything, please don't hesitate. Phone or SMS is best. - http://www.jspiro.com/ shows you my Canadian number. - My American number is in an IRC PM which I sent to RyanVM just before I quit my IRC client. - Both numbers accept calls and SMSes. Email might take much longer.
My American number will also be viewable at https://pastebin.com/1uR0bGAa for the next two weeks.
P.S. There is no need to create a new bug and mark old one as duplicate, because it could be tracked in old one.
No longer blocks: 1323069
Status: ASSIGNED → RESOLVED
Crash Signature: [@ RefPtr<T>::assign_assuming_AddRef | mozilla::a11y::LazyInstantiator::AccumulateTelemetry] [@ base::Histogram::SampleSet::Resize ] [@ mozilla::a11y::LazyInstantiator::AccumulateTelemetry ] [@ nsCOMPtr_base::assign_assuming_AddRef | mozilla::a11y::Laz…
Closed: 7 years ago
Resolution: --- → DUPLICATE
See Also: 1375130 →
(In reply to Virtual_ManPL [:Virtual] - (please needinfo? me - so I will see your comment/reply/question/etc.) from comment #4) > P.S. There is no need to create a new bug and mark old one as duplicate, > because it could be tracked in old one. I was unaware of bug 1375412 at the time; this one was filed in response to the reopening of bug 1323069. Only later did I connect bug 1375412 to this. Having said that, I am not sure what you are trying to achieve by changing out which bug is duped by which; I was just about to upload a patch to this one.
You need to log in before you can comment on or make changes to this bug.