Closed Bug 1213605 Opened 9 years ago Closed 9 years ago

crash in memmove | nsACString_internal::Assign(nsACString_internal const&) | mozilla::layers::FrameMetrics::operator=(mozilla::layers::FrameMetrics const&)

Categories

(Core :: Graphics: Layers, defect)

Unspecified
Windows
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1213273
Tracking Status
firefox44 - affected

People

(Reporter: MatsPalmgren_bugz, Assigned: botond)

References

Details

(Keywords: crash, regression, steps-wanted)

Crash Data

This bug was filed from the Socorro interface and is report bp-d182b58b-75c1-4a3a-9c1e-f3a9a2151009. ============================================================= This looks like a recent regression in v44. The first crash occurred in build 2015092903. It's currently at #10 in the Top Crash list for v44. I suspect #9 "memmove" is likely the same bug, but the stack is damaged in those reports. (Together these would be at #3.) All crashes are on Windows. memmove @0xa080fc276f nsACString_internal::Assign(nsACString_internal const&) mozilla::layers::FrameMetrics::operator=(mozilla::layers::FrameMetrics const&) mozilla::layers::AsyncPanZoomController::DispatchRepaintRequest(mozilla::layers::FrameMetrics const&) RunnableMethod<mozilla::layers::InputQueue, void ( mozilla::layers::InputQueue::*)(unsigned __int64 const&), Tuple1<unsigned __int64> >::Run() mozilla::layers::TaskThrottler::RunQueuedTask(mozilla::TimeStamp const&) mozilla::layers::GenericTimerCallback<<lambda_4b0fa8e08e9d3b1658dc496dfec1bce8> >::Notify(nsITimer*) nsTimerImpl::Fire() ... More Reports: https://crash-stats.mozilla.com/report/list?product=Firefox&signature=memmove+%7C+nsACString_internal%3A%3AAssign%28nsACString_internal+const%26%29+%7C+mozilla%3A%3Alayers%3A%3AFrameMetrics%3A%3Aoperator%3D%28mozilla%3A%3Alayers%3A%3AFrameMetrics+const%26%29
[Tracking Requested - why for this release]: recent crash regression
Crash Signature: [@ memmove | nsACString_internal::Assign(nsACString_internal const&) | mozilla::layers::FrameMetrics::operator=(mozilla::layers::FrameMetrics const&)] → [@ memmove | nsACString_internal::Assign(nsACString_internal const&) | mozilla::layers::FrameMetrics::operator=(mozilla::layers::FrameMetrics const&)] [@ memmove | nsACString_internal::Assign | mozilla::layers::FrameMetrics::operator=]
Here is the pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6256ec9113c115141aab089c45ee69438884b680&tochange=acdb22976ff86539dc10413c5f366e1fb429a680 Unfortunately the list of changes is too long to be useful. This needs steps to reproduce so it can be regressed further on mozilla-inbound.
Keywords: steps-wanted
OS: Windows NT → Windows
Bug 1207270 seems like a good candidate. Botond, given that kats is on PTO, can you take a look?
Flags: needinfo?(botond)
The regressing bug is almost certainly bug 1207270. The issue may be related to bug 1213273. I will investigate.
Assignee: nobody → botond
Flags: needinfo?(botond)
I have a candidate patch in bug 1213273 which I'm hoping fixes both problems.
(In reply to Botond Ballo [:botond] from comment #5) > I have a candidate patch in bug 1213273 which I'm hoping fixes both problems. Thanks Botond, let's hope so.
Depends on: 1213273
According to crash-stats it looks like this stopped happening after the 20151006030231 build. Please reopen if I'm mistaken.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
This is more specifically a duplicate of bug 1213273, as the crashing code path was removed in that patch.
Resolution: WORKSFORME → DUPLICATE
We don't need to track this as it's a duplicate and bug 1213273 has already been fixed.
You need to log in before you can comment on or make changes to this bug.