Updates:
Summary: Chrome: Crash Report - Crash calling std::stable_sort under
RenderLayer::updateZOrderLists()
Comment #3 on issue 7829 by [email protected]: Chrome: Crash Report -
Crash calling std::stable_sort under RenderLayer::updateZOrderLists()
http://code.google.com/p/chromium/issues/detail?id=7829
The stack being junk is just due to how the linker deals with templates.
It's
sqaushed a bunch of symbols together and our stack crawl doesn't know which
one is
which. The real crash point is here:
void RenderLayer::updateZOrderLists()
{
if (!isStackingContext() || !m_zOrderListsDirty)
return;
for (RenderLayer* child = firstChild(); child; child =
child->nextSibling())
if (!m_reflection || reflectionLayer() != child)
child->collectLayers(m_posZOrderList, m_negZOrderList);
// Sort the two lists.
if (m_posZOrderList)
std::stable_sort(m_posZOrderList->begin(), m_posZOrderList->end(),
compareZIndex);
if (m_negZOrderList)
std::stable_sort(m_negZOrderList->begin(), m_negZOrderList->end(),
compareZIndex);
m_zOrderListsDirty = false;
}
Which one of those two std::stable_sort calls is crashing I don't know w/o
looking
closer at the line numbers.
I expect that one of the lists:
Vector<RenderLayer*>* m_posZOrderList;
Vector<RenderLayer*>* m_negZOrderList;
is somehow trashed. Possibly the layer itself is already trashed. One
would need to
look further up the stack trace.
A reproducible case or website would help here.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
