Android webkit image的加载过程解析（二）

最新推荐文章于 2021-09-15 19:16:34 发布
最新推荐文章于 2021-09-15 19:16:34 发布
阅读量2.3k 收藏 1
点赞数
分类专栏： 浏览器开发详解 文章标签： android 渲染图片 android browser imag android browser rend android webkit rende android browser
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/ChaoY1116/article/details/16882957
版权

 

还是顺着前面的内容进行分析，前面一篇文章中，是对image标签进行了解析。我们分析了一个img的标签，其所对应的资源被下载的全过程。

当我们load img标签的时候，我们会发现进行了预下载的工作。
这也被我们判断为webkit渲染速度比其它引擎快速的一个原因。毕竟直接从cache里面读取是比从网络上下载要快非常多的。
而当我们load之后，接下来进行的工作是什么呢？图片到底是怎么被显示在终端上面的呢？
下面准备接着对这样的内容进行分析。

(gdb) bt
#0  WebCore::RenderImage::paint (this=0x2a4fd634, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderImage.cpp:330
#1  0x48d98538 in WebCore::InlineBox::paint (this=0x2a4e4f44, paintInfo=<value optimized out>, tx=<value optimized out>, ty=<value optimized out>)
    at external/webkit/Source/WebCore/rendering/InlineBox.cpp:184
#2  WebCore::InlineBox::paint (this=0x2a4e4f44, paintInfo=<value optimized out>, tx=<value optimized out>, ty=<value optimized out>) at external/webkit/Source/WebCore/rendering/InlineBox.cpp:162
#3  0x48d9b7a0 in WebCore::InlineFlowBox::paint (this=<value optimized out>, paintInfo=..., tx=0, ty=0, lineTop=33, lineBottom=52) at external/webkit/Source/WebCore/rendering/InlineFlowBox.cpp:1014
#4  0x48df7bfa in WebCore::RootInlineBox::paint (this=0x2a4e4f6c, paintInfo=..., tx=0, ty=0, lineTop=33, lineBottom=52) at external/webkit/Source/WebCore/rendering/RootInlineBox.cpp:183
#5  0x48dd1618 in WebCore::RenderLineBoxList::paint (this=0x2a4fd628, renderer=0x2a4fd5b8, paintInfo=<value optimized out>, tx=0, ty=0)
        at external/webkit/Source/WebCore/rendering/RenderLineBoxList.cpp:262
#6  0x48da1b9c in WebCore::RenderBlock::paintContents (this=0x2a4fd5b8, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2422
#7  WebCore::RenderBlock::paintContents (this=0x2a4fd5b8, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2413
#8  0x48da9e8a in WebCore::RenderBlock::paintObject (this=0x2a4fd5b8, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2536
#9  0x48da0a50 in WebCore::RenderBlock::paint (this=0x2a4fd5b8, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2312
#10 0x48da1ad8 in WebCore::RenderBlock::paintChildren (this=0x2a4fd244, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2465
#11 0x48da9e8a in WebCore::RenderBlock::paintObject (this=0x2a4fd244, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2536
#12 0x48da0a50 in WebCore::RenderBlock::paint (this=0x2a4fd244, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2312
#13 0x48da1ad8 in WebCore::RenderBlock::paintChildren (this=0x2a4fd1c8, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2465
#14 0x48da9e8a in WebCore::RenderBlock::paintObject (this=0x2a4fd1c8, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2536
#15 0x48da0a50 in WebCore::RenderBlock::paint (this=0x2a4fd1c8, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2312
#16 0x48da1ad8 in WebCore::RenderBlock::paintChildren (this=0x2a4fd06c, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2465
#17 0x48da9e8a in WebCore::RenderBlock::paintObject (this=0x2a4fd06c, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2536
#18 0x48da0a50 in WebCore::RenderBlock::paint (this=0x2a4fd06c, paintInfo=..., tx=0, ty=0) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:2312
#19 0x48dcc43c in WebCore::RenderLayer::paintLayer (this=<value optimized out>, rootLayer=0x2a4fcf8c, p=<value optimized out>, paintDirtyRect=..., paintBehavior=0, paintingRoot=0x0, 
            overlapTestRequests=0x4a8c2644, paintFlags=<value optimized out>) at external/webkit/Source/WebCore/rendering/RenderLayer.cpp:2725
#20 0x48dcc996 in WebCore::RenderLayer::paintList (this=0x2a4fcf8c, list=0x2a4d2758, rootLayer=0x2a4fcf8c, p=0x4a8c2758, paintDirtyRect=..., paintBehavior=0, paintingRoot=0x0, 
                overlapTestRequests=0x4a8c2644, paintFlags=0) at external/webkit/Source/WebCore/rendering/RenderLayer.cpp:2784
#21 0x48dcc4f8 in WebCore::RenderLayer::paintLayer (this=<value optimized out>, rootLayer=0x2a4fcf8c, p=<value optimized out>, paintDirtyRect=..., paintBehavior=0, paintingRoot=0x0, 
                    overlapTestRequests=0x4a8c2644, paintFlags=<value optimized out>) at external/webkit/Source/WebCore/rendering/RenderLayer.cpp:2746
#22 0x48dcca28 in WebCore::RenderLayer::paint (this=<value optimized out>, p=0x4a8c2758, damageRect=..., paintBehavior=<value optimized out>, paintingRoot=0x0)
                        at external/webkit/Source/WebCore/rendering/RenderLayer.cpp:2519
#23 0x48d62b76 in WebCore::FrameView::paintContents (this=0x2a4faf40, p=0x4a8c2758, rect=...) at external/webkit/Source/WebCore/page/FrameView.cpp:2424
#24 0x48e4c5ac in android::WebFrameView::draw (this=<value optimized out>, gc=0x4a8c2758, rect=...) at external/webkit/Source/WebKit/android/jni/WebFrameView.cpp:61
#25 0x48e4f7bc in android::WebViewCore::paintContents (this=<value optimized out>, gc=0x4a8c2758, dirty=...) at external/webkit/Source/WebKit/android/jni/WebViewCore.cpp:751
#26 0x48f92832 in WebCore::PicturePile::updatePicture (this=<value optimized out>, painter=0x2a0c7788, pc=...) at external/webkit/Source/WebKit/android/jni/PicturePile.cpp:199
#27 0x48f92f78 in WebCore::PicturePile::updatePicturesIfNeeded (this=0x2a0c77a4, painter=0x2a0c7788) at external/webkit/Source/WebKit/android/jni/PicturePile.cpp:160
#28 0x48e4fdb8 in android::WebViewCore::recordPicturePile (this=0x2a0c7780) at external/webkit/Source/WebKit/android/jni/WebViewCore.cpp:722
#29 0x48e56068 in android::WebViewCore::recordContent (this=0x2a0c7780, point=0x4a8c2c48) at external/webkit/Source/WebKit/android/jni/WebViewCore.cpp:915
#30 0x48e560a0 in RecordContent (env=0x2a11f140, obj=<value optimized out>, nativeClass=<value optimized out>, pt=0x36300005) at external/webkit/Source/WebKit/android/jni/WebViewCore.cpp:4549
#31 0x4070fe34 in dvmPlatformInvoke () at dalvik/vm/arch/arm/CallEABI.S:258
#32 0x4073ee6a in dvmCallJNIMethod (args=0x4a3a8e20, pResult=0x2a1118a0, method=0x44da09c8, self=0x2a111890) at dalvik/vm/Jni.cpp:1155
#33 0x4072ad88 in dvmCheckCallJNIMethod (args=<value optimized out>, pResult=0x2a1118a0, method=0x44da09c8, self=0x2a111890) at dalvik/vm/CheckJni.cpp:145
#34 0x40719264 in dalvik_mterp () at dalvik/vm/mterp/out/InterpAsm-armv7-a.S:16239
#35 0x4071db30 in dvmInterpret (self=0x2a111890, method=<value optimized out>, pResult=0x4a8c2eb0) at dalvik/vm/interp/Interp.cpp:1964
#36 0x40751594 in dvmCallMethodV (self=0x2a111890, method=0x44bf1d40, obj=<value optimized out>, fromJni=<value optimized out>, pResult=0x4a8c2eb0, args=...) at dalvik/vm/interp/Stack.cpp:526
#37 0x407515be in dvmCallMethod (self=<value optimized out>, method=<value optimized out>, obj=<value optimized out>, pResult=0x4a8c2eb0) at dalvik/vm/interp/Stack.cpp:429
#38 0x40746176 in interpThreadStart (arg=0x2a111890) at dalvik/vm/Thread.cpp:1538
#39 0x40038db4 in __thread_entry (func=0x407460d5 <interpThreadStart>, arg=0x2a111890, tls=<value optimized out>) at bionic/libc/bionic/pthread.c:217
#40 0x40038518 in pthread_create (thread_out=0x2a0ddbf0, attr=0xbee99818, start_routine=0x407460d5 <interpThreadStart>, arg=0x2a111890) at bionic/libc/bionic/pthread.c:356


这是一个非常复杂的backtrace....
但是我们没有必要紧张，可以一点一点的来看这个问题：

 

#30 0x48e560a0 in RecordContent (env=0x2a11f140, obj=<value optimized out>, nativeClass=<value optimized out>, pt=0x36300005) at external/webkit/Source/WebKit/android/jni/WebViewCore.cpp:4549


一看这个函数我们就知道涉及到的是JNI的操作了。
查看一下对应关系：  { "nativeRecordContent", "(ILandroid/graphics/Point;)I", (void*) RecordContent },
看到native函数，我们就明白了这个函数其实是由java端对native层的调用了。
继续来追一下这个调用：
    WebViewCore.java中对native函数的调用有两处，
    1. private void webkitDraw() 
    2. private void saveViewState(OutputStream stream, ValueCallback<Boolean> callback)
经过debug，我们发现在正常打开一个网页的时候，主要进行的是webkitDraw的操作。

所以我们继续追踪一下webkitDraw的调用过成。

 

case WEBKIT_DRAW:
    webkitDraw();
    break;

可以看到，在接受到WEBKIT_DRAW的信号的时候，就会进行webkitDraw的工作。那么，在我们正常加载一张图片的时候，这个信息是由谁发出的呢？
有三个地方对WEBKIT_DRAW的信号进行了发送的通知，分别是：
    void contentDraw() 
    void resumeWebKitDraw() 
    void webkitDraw() 
这边我们主要关心的是contentDraw()。
看到contentDraw函数的注释就可以知道这个函数called from JNI or WebView thread。
相对应的，我们在webviewcore.cpp里面找到了向对应的函数：

 

void WebViewCore::contentDraw()
{
    JNIEnv* env = JSC::Bindings::getJNIEnv();
    AutoJObject javaObject = m_javaGlue->object(env);
    if (!javaObject.get())
        return;
    env->CallVoidMethod(javaObject.get(), m_javaGlue->m_contentDraw);
    checkException(env);
}

既然找到了在native的接口，那么我们先研究一下调用到这边函数的一个过程，然后再去研究上面的那一个复杂的堆栈。

这边我们以打开一个google的网页为例进行说明。 （此时的cache，data都已经清零）

这个比刚才的backtrace还要复杂的堆栈是出现在第一次断点被断掉的地方。。。

虽然堆栈很多也很大，但是这边有很多我们已经分析过的log。
起码到WebCore::HTMLTreeBuilder::processStartTagForInBody之前的log，我们应该已经非常的熟悉了。
而

 

#17 0x48fc6476 in WebCore::HTMLConstructionSite::attach<WebCore::Element> (this=<value optimized out>, rawParent=0x2a421148, prpChild=<value optimized out>)
                    at external/webkit/Source/WebCore/html/parser/HTMLConstructionSite.cpp:108
#18 0x48fc64ae in WebCore::HTMLConstructionSite::attachToCurrent (this=<value optimized out>, child=<value optimized out>) at external/webkit/Source/WebCore/html/parser/HTMLConstructionSite.cpp:260
#19 0x48fc6512 in WebCore::HTMLConstructionSite::insertHTMLElement (this=0x2a1fa59c, token=<value optimized out>) at external/webkit/Source/WebCore/html/parser/HTMLConstructionSite.cpp:290
#20 0x48f2fcde in WebCore::HTMLTreeBuilder::processStartTagForInBody (this=<value optimized out>, token=...) at external/webkit/Source/WebCore/html/parser/HTMLTreeBuilder.cpp:1032

这个堆栈我们应该也不会感到陌生。
在
if (parent->attached() && !child->attached())
    child->attach();
的操作中，因为child是一个Element类型的变量，所以这边会去调用Element类中的attached方法。
attached是一个非常非常重要的方法, 函数原型为：

 

void Element::attach()
{
    suspendPostAttachCallbacks();
    RenderWidget::suspendWidgetHierarchyUpdates(); //RenderWidget类主要负责的作用是负责调度页面渲染和页面更新等操作。


    createRendererIfNeeded();// 非常重要的函数,判断当前的节点是否需要渲染


    StyleSelectorParentPusher parentPusher(this);


    if (Node* shadow = shadowRoot()) {
        parentPusher.push();
        shadow->attach();
    }


    if (firstChild())
        parentPusher.push();
    ContainerNode::attach();


    if (hasRareData()) {
        ElementRareData* data = rareData();
        if (data->needsFocusAppearanceUpdateSoonAfterAttach()) {
            if (isFocusable() && document()->focusedNode() == this)
                document()->updateFocusAppearanceSoon(false /* don't restore selection */);
            data->setNeedsFocusAppearanceUpdateSoonAfterAttach(false);
        }
    }


    RenderWidget::resumeWidgetHierarchyUpdates();
    resumePostAttachCallbacks();
}

在这个函数中，我们首先关心的是createRendererIfNeeded()。
函数的实现在Node.cpp,函数的原型为：

 

void Node::createRendererIfNeeded()
{
    if (!document()->shouldCreateRenderers()) //判断当前的节点是否需要Renderers，如果不需要的话就直接返回。
        return;


    ASSERT(!renderer());


    RenderObject* newRenderer = createRendererAndStyle();  //RenderObject类的作用是所有RenderTree的基类,类似Node在Dom中的作用
            
#if ENABLE(FULLSCREEN_API)
    if (document()->webkitIsFullScreen() && document()->webkitCurrentFullScreenElement() == this)
        newRenderer = wrapWithRenderFullScreen(newRenderer, document());
#endif


    if (!newRenderer) //如果newRenderer没有创建成功的话，就返回。 容错判断
        return;


    // Note: Adding newRenderer instead of renderer(). renderer() may be a child of newRenderer.
    parentNodeForRenderingAndStyle()->renderer()->addChild(newRenderer, nextRenderer());
}

Node::createRendererAndStyle()的实现中，我们会进行RefPtr<RenderStyle> style = styleForRenderer()的操作。RenderStyle的作用是什么呢？这个往往用来描述一个RenderObject所可能涉及的CSS属性数据，也就是说在这个style里面，我们已经保存了当前节点的css的相关属性。这边获取css的属性方面也很复杂，不过相比与现在分析的这个Image的渲染过程还是相对应比较简单的。
在style创建完成之后，RenderObject* newRenderer = createRenderer(document()->renderArena(), style.get());就会获取当前的style的相关属性并且赋值给newRenderer，这样的话，函数返回值的newRenderer已经包含了当前dom树的属性，并且同步具有了css的相关属性。

在创建完RenderObject对象之后，会对RenderObject对象设置RenderStyle属性，然后在该DOM Node的父节点对应的RenderObject中添加刚刚新建的RenderObject，这样的作用是用于构建RenderTree。
是否可以认为在createRendererIfNeeded之后，当前节点已经插入到了RenderTree中呢？  接下来接着分析。

 

#0  android::WebViewCore::contentDraw (this=0x2a1c6f68) at external/webkit/Source/WebKit/android/jni/WebViewCore.cpp:969
#1  0x48f8ad3c in android::ChromeClientAndroid::attachRootGraphicsLayer (this=<value optimized out>, layer=<value optimized out>)
    at external/webkit/Source/WebKit/android/WebCoreSupport/ChromeClientAndroid.cpp:112
#2  0x48dcfd8c in WebCore::RenderLayerCompositor::attachRootPlatformLayer (this=0x2a3b3f58, attachment=WebCore::RenderLayerCompositor::RootLayerAttachedViaChromeClient)
        at external/webkit/Source/WebCore/rendering/RenderLayerCompositor.cpp:1895
    #3  0x48dd03e4 in WebCore::RenderLayerCompositor::ensureRootPlatformLayer (this=0x2a3b3f58) at external/webkit/Source/WebCore/rendering/RenderLayerCompositor.cpp:1842
#4  0x48dd0432 in WebCore::RenderLayerCompositor::enableCompositingMode (this=0x2a3b3f58, enable=<value optimized out>) at external/webkit/Source/WebCore/rendering/RenderLayerCompositor.cpp:153
#5  WebCore::RenderLayerCompositor::enableCompositingMode (this=0x2a3b3f58, enable=<value optimized out>) at external/webkit/Source/WebCore/rendering/RenderLayerCompositor.cpp:147
#6  0x48dd051a in WebCore::RenderLayerCompositor::updateBacking (this=0x2a3b3f58, layer=0x2a3fa67c, shouldRepaint=WebCore::RenderLayerCompositor::CompositingChangeRepaintNow)
            at external/webkit/Source/WebCore/rendering/RenderLayerCompositor.cpp:360
#7  0x48dd05da in WebCore::RenderLayerCompositor::updateLayerCompositingState (this=<value optimized out>, layer=0x2a3fa67c, shouldRepaint=<value optimized out>)
                at external/webkit/Source/WebCore/rendering/RenderLayerCompositor.cpp:437
#8  0x48dca85a in WebCore::RenderLayer::styleChanged (this=0x2a3fa67c, diff=WebCore::StyleDifferenceEqual, oldStyle=0x0) at external/webkit/Source/WebCore/rendering/RenderLayer.cpp:4119
#9  0x48db78e6 in WebCore::RenderBoxModelObject::styleDidChange (this=0x2a3fa600, diff=WebCore::StyleDifferenceEqual, oldStyle=0x0) at external/webkit/Source/WebCore/rendering/RenderBoxModelObject.cpp:363
#10 0x48db2122 in WebCore::RenderBox::styleDidChange (this=0x2a3fa600, diff=<value optimized out>, oldStyle=0x0) at external/webkit/Source/WebCore/rendering/RenderBox.cpp:300
#11 0x48da903a in WebCore::RenderBlock::styleDidChange (this=0x2a3fa600, diff=WebCore::StyleDifferenceEqual, oldStyle=<value optimized out>) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:239
#12 0x48dd998a in WebCore::RenderObject::setStyle (this=0x2a3fa600, style=<value optimized out>) at external/webkit/Source/WebCore/rendering/RenderObject.cpp:1634
#13 0x48dd9260 in WebCore::RenderObject::setAnimatableStyle (this=0x2a3fa600, style=<value optimized out>) at external/webkit/Source/WebCore/rendering/RenderObject.cpp:1551
#14 0x48d06d82 in WebCore::Node::createRendererAndStyle (this=0x2a42fb70) at external/webkit/Source/WebCore/dom/Node.cpp:1508
#15 0x48d06de2 in WebCore::Node::createRendererIfNeeded (this=0x2a42fb70) at external/webkit/Source/WebCore/dom/Node.cpp:1533
#16 0x48ef01a2 in WebCore::Element::attach (this=0x2a42fb70) at external/webkit/Source/WebCore/dom/Element.cpp:991
#17 0x48fc6476 in WebCore::HTMLConstructionSite::attach<WebCore::Element> (this=<value optimized out>, rawParent=0x2a421148, prpChild=<value optimized out>)
                    at external/webkit/Source/WebCore/html/parser/HTMLConstructionSite.cpp:108
#18 0x48fc64ae in WebCore::HTMLConstructionSite::attachToCurrent (this=<value optimized out>, child=<value optimized out>) at external/webkit/Source/WebCore/html/parser/HTMLConstructionSite.cpp:260
#19 0x48fc6512 in WebCore::HTMLConstructionSite::insertHTMLElement (this=0x2a1fa59c, token=<value optimized out>) at external/webkit/Source/WebCore/html/parser/HTMLConstructionSite.cpp:290
#20 0x48f2fcde in WebCore::HTMLTreeBuilder::processStartTagForInBody (this=<value optimized out>, token=...) at external/webkit/Source/WebCore/html/parser/HTMLTreeBuilder.cpp:1032
#21 0x48f30caa in WebCore::HTMLTreeBuilder::processStartTag (this=0x2a1fa588, token=...) at external/webkit/Source/WebCore/html/parser/HTMLTreeBuilder.cpp:1338
#22 0x48f32424 in WebCore::HTMLTreeBuilder::constructTreeFromAtomicToken (this=0x2a1fa588, token=<value optimized out>) at external/webkit/Source/WebCore/html/parser/HTMLTreeBuilder.cpp:462
#23 0x48f3255a in WebCore::HTMLTreeBuilder::constructTreeFromToken (this=0x2a1fa588, rawToken=...) at external/webkit/Source/WebCore/html/parser/HTMLTreeBuilder.cpp:452
#24 0x48f26aba in WebCore::HTMLDocumentParser::pumpTokenizer (this=0x2a3fb1f8, mode=WebCore::HTMLDocumentParser::AllowYield) at external/webkit/Source/WebCore/html/parser/HTMLDocumentParser.cpp:276
#25 0x48f26d52 in WebCore::HTMLDocumentParser::append (this=0x2a3fb1f8, source=...) at external/webkit/Source/WebCore/html/parser/HTMLDocumentParser.cpp:367
#26 WebCore::HTMLDocumentParser::append (this=0x2a3fb1f8, source=...) at external/webkit/Source/WebCore/html/parser/HTMLDocumentParser.cpp:337
#27 0x48fbe314 in WebCore::DecodedDataDocumentParser::appendBytes (this=0x2a3fb1f8, writer=<value optimized out>, 
                        data=0x2a3e95c0 "agName&&\"click\"==k&&(a.preventDefault?a.preventDefault():a.returnValue=!1),d.d)d.d(b);else{var s;if((e=c.document)&&!e.createEvent&&e.createEventObject)try{s=e.createEventObject(a)}catch(U){s=a}else s"..., length=2230, shouldFlush=false) at external/webkit/Source/WebCore/dom/DecodedDataDocumentParser.cpp:54
#28 0x48f3853a in WebCore::DocumentWriter::addData (this=0x2a2ebf8c, 
                            str=0x2a3e95c0 "agName&&\"click\"==k&&(a.preventDefault?a.preventDefault():a.returnValue=!1),d.d)d.d(b);else{var s;if((e=c.document)&&!e.createEvent&&e.createEventObject)try{s=e.createEventObject(a)}catch(U){s=a}else s"..., len=2230, flush=<value optimized out>) at external/webkit/Source/WebCore/loader/DocumentWriter.cpp:207
#29 0x48f36c8c in WebCore::DocumentLoader::commitData (this=0x2a2ebf38, 
                                bytes=0x2a3e95c0 "agName&&\"click\"==k&&(a.preventDefault?a.preventDefault():a.returnValue=!1),d.d)d.d(b);else{var s;if((e=c.document)&&!e.createEvent&&e.createEventObject)try{s=e.createEventObject(a)}catch(U){s=a}else s"..., length=2230) at external/webkit/Source/WebCore/loader/DocumentLoader.cpp:321
#30 0x48f8beac in android::FrameLoaderClientAndroid::committedLoad (this=0x2a032940, loader=0x2a2ebf38, 
                                    data=0x2a3e95c0 "agName&&\"click\"==k&&(a.preventDefault?a.preventDefault():a.returnValue=!1),d.d)d.d(b);else{var s;if((e=c.document)&&!e.createEvent&&e.createEventObject)try{s=e.createEventObject(a)}catch(U){s=a}else s"..., length=2230) at external/webkit/Source/WebKit/android/WebCoreSupport/FrameLoaderClientAndroid.cpp:732
#31 0x48f36abc in WebCore::DocumentLoader::commitLoad (this=0x2a2ebf38, 
                                        data=0x2a3e95c0 "agName&&\"click\"==k&&(a.preventDefault?a.preventDefault():a.returnValue=!1),d.d)d.d(b);else{var s;if((e=c.document)&&!e.createEvent&&e.createEventObject)try{s=e.createEventObject(a)}catch(U){s=a}else s"..., length=2230) at external/webkit/Source/WebCore/loader/DocumentLoader.cpp:307
#32 0x48d51310 in WebCore::ResourceLoader::didReceiveData (this=0x2a2eac88, 
                                            data=0x2a3e95c0 "agName&&\"click\"==k&&(a.preventDefault?a.preventDefault():a.returnValue=!1),d.d)d.d(b);else{var s;if((e=c.document)&&!e.createEvent&&e.createEventObject)try{s=e.createEventObject(a)}catch(U){s=a}else s"..., length=2230, encodedDataLength=2230, allAtOnce=false) at external/webkit/Source/WebCore/loader/ResourceLoader.cpp:288
#33 0x48f38d1a in WebCore::MainResourceLoader::didReceiveData (this=<value optimized out>, 
                                                data=0x2a3e95c0 "agName&&\"click\"==k&&(a.preventDefault?a.preventDefault():a.returnValue=!1),d.d)d.d(b);else{var s;if((e=c.document)&&!e.createEvent&&e.createEventObject)try{s=e.createEventObject(a)}catch(U){s=a}else s"..., length=2230, encodedDataLength=2230, allAtOnce=false) at external/webkit/Source/WebCore/loader/MainResourceLoader.cpp:454
#34 0x48d5104e in WebCore::ResourceLoader::didReceiveData (this=<value optimized out>, data=<value optimized out>, length=<value optimized out>, encodedDataLength=2230)
                                                    at external/webkit/Source/WebCore/loader/ResourceLoader.cpp:439
                                                    ---Type <return> to continue, or q <return> to quit---
#35 0x48e4229a in android::WebUrlLoaderClient::didReceiveData (this=0x2a3052b8, buf=<value optimized out>, size=2230) at external/webkit/Source/WebKit/android/WebCoreSupport/WebUrlLoaderClient.cpp:398
#36 0x48e441b2 in DispatchToMethod<android::WebUrlLoaderClient, void (android::WebUrlLoaderClient::*)(scoped_refptr<net::IOBuffer>, int), scoped_refptr<net::IOBuffer>, int> (this=0x2a1ffad0)
                                                        at external/chromium/base/tuple.h:558
#37 RunnableMethod<android::WebUrlLoaderClient, void (android::WebUrlLoaderClient::*)(scoped_refptr<net::IOBuffer>, int), Tuple2<scoped_refptr<net::IOBuffer>, int> >::Run (this=0x2a1ffad0)
                                                            at external/chromium/base/task.h:332
#38 0x48e41f1a in RunTask (v=<value optimized out>) at external/webkit/Source/WebKit/android/WebCoreSupport/WebUrlLoaderClient.cpp:343
#39 0x48d0045a in WTF::dispatchFunctionsFromMainThread () at external/webkit/Source/JavaScriptCore/wtf/MainThread.cpp:155
#40 0x48e48cbe in android::JavaSharedClient::ServiceFunctionPtrQueue () at external/webkit/Source/WebKit/android/jni/JavaSharedClient.cpp:134
#41 0x4070fe34 in dvmPlatformInvoke () at dalvik/vm/arch/arm/CallEABI.S:258
#42 0x4073ee6a in dvmCallJNIMethod (args=0x4abd2f28, pResult=0x2a098700, method=0x44d9cf40, self=0x2a0986f0) at dalvik/vm/Jni.cpp:1155
#43 0x4072ad88 in dvmCheckCallJNIMethod (args=<value optimized out>, pResult=0x2a098700, method=0x44d9cf40, self=0x2a0986f0) at dalvik/vm/CheckJni.cpp:145
#44 0x40719264 in dalvik_mterp () at dalvik/vm/mterp/out/InterpAsm-armv7-a.S:16239
#45 0x4071db30 in dvmInterpret (self=0x2a0986f0, method=<value optimized out>, pResult=0x4acd2eb0) at dalvik/vm/interp/Interp.cpp:1964
#46 0x40751594 in dvmCallMethodV (self=0x2a0986f0, method=0x44bf1d40, obj=<value optimized out>, fromJni=<value optimized out>, pResult=0x4acd2eb0, args=...) at dalvik/vm/interp/Stack.cpp:526
#47 0x407515be in dvmCallMethod (self=<value optimized out>, method=<value optimized out>, obj=<value optimized out>, pResult=0x4acd2eb0) at dalvik/vm/interp/Stack.cpp:429
#48 0x40746176 in interpThreadStart (arg=0x2a0986f0) at dalvik/vm/Thread.cpp:1538
#49 0x40038db4 in __thread_entry (func=0x407460d5 <interpThreadStart>, arg=0x2a0986f0, tls=<value optimized out>) at bionic/libc/bionic/pthread.c:217
#50 0x40038518 in pthread_create (thread_out=0x2a146578, attr=0xbe975818, start_routine=0x407460d5 <interpThreadStart>, arg=0x2a0986f0) at bionic/libc/bionic/pthread.c:356
#51 0x2a0f45f8 in ?? ()
                                                            Cannot access memory at address 0x0
#52 0x2a0f45f8 in ?? ()
                                                            Cannot access memory at address 0x0
                                                            Backtrace stopped: previous frame identical to this frame (corrupt stack?)

经过刚才的分析，我们的堆栈只剩下了下面的部分：

 

#0  android::WebViewCore::contentDraw (this=0x2a1c6f68) at external/webkit/Source/WebKit/android/jni/WebViewCore.cpp:969                                                                                     
#1  0x48f8ad3c in android::ChromeClientAndroid::attachRootGraphicsLayer (this=<value optimized out>, layer=<value optimized out>)
    at external/webkit/Source/WebKit/android/WebCoreSupport/ChromeClientAndroid.cpp:112
#2  0x48dcfd8c in WebCore::RenderLayerCompositor::attachRootPlatformLayer (this=0x2a3b3f58, attachment=WebCore::RenderLayerCompositor::RootLayerAttachedViaChromeClient)
            at external/webkit/Source/WebCore/rendering/RenderLayerCompositor.cpp:1895
                #3  0x48dd03e4 in WebCore::RenderLayerCompositor::ensureRootPlatformLayer (this=0x2a3b3f58) at external/webkit/Source/WebCore/rendering/RenderLayerCompositor.cpp:1842
#4  0x48dd0432 in WebCore::RenderLayerCompositor::enableCompositingMode (this=0x2a3b3f58, enable=<value optimized out>) at external/webkit/Source/WebCore/rendering/RenderLayerCompositor.cpp:153
#5  WebCore::RenderLayerCompositor::enableCompositingMode (this=0x2a3b3f58, enable=<value optimized out>) at external/webkit/Source/WebCore/rendering/RenderLayerCompositor.cpp:147
#6  0x48dd051a in WebCore::RenderLayerCompositor::updateBacking (this=0x2a3b3f58, layer=0x2a3fa67c, shouldRepaint=WebCore::RenderLayerCompositor::CompositingChangeRepaintNow)
                            at external/webkit/Source/WebCore/rendering/RenderLayerCompositor.cpp:360
#7  0x48dd05da in WebCore::RenderLayerCompositor::updateLayerCompositingState (this=<value optimized out>, layer=0x2a3fa67c, shouldRepaint=<value optimized out>)
                                            at external/webkit/Source/WebCore/rendering/RenderLayerCompositor.cpp:437
#8  0x48dca85a in WebCore::RenderLayer::styleChanged (this=0x2a3fa67c, diff=WebCore::StyleDifferenceEqual, oldStyle=0x0) at external/webkit/Source/WebCore/rendering/RenderLayer.cpp:4119
#9  0x48db78e6 in WebCore::RenderBoxModelObject::styleDidChange (this=0x2a3fa600, diff=WebCore::StyleDifferenceEqual, oldStyle=0x0) at external/webkit/Source/WebCore/rendering/RenderBoxModelObject.cpp:363
#10 0x48db2122 in WebCore::RenderBox::styleDidChange (this=0x2a3fa600, diff=<value optimized out>, oldStyle=0x0) at external/webkit/Source/WebCore/rendering/RenderBox.cpp:300
#11 0x48da903a in WebCore::RenderBlock::styleDidChange (this=0x2a3fa600, diff=WebCore::StyleDifferenceEqual, oldStyle=<value optimized out>) at external/webkit/Source/WebCore/rendering/RenderBlock.cpp:239
#12 0x48dd998a in WebCore::RenderObject::setStyle (this=0x2a3fa600, style=<value optimized out>) at external/webkit/Source/WebCore/rendering/RenderObject.cpp:1634
#13 0x48dd9260 in WebCore::RenderObject::setAnimatableStyle (this=0x2a3fa600, style=<value optimized out>) at external/webkit/Source/WebCore/rendering/RenderObject.cpp:1551
#14 0x48d06d82 in WebCore::Node::createRendererAndStyle (this=0x2a42fb70) at external/webkit/Source/WebCore/dom/Node.cpp:1508

到了这一步的话，可能就不那么让人感觉繁琐了。
在刚才分析了newRenderer创建之后，通过backtrace，我们发现setAnimatableStyle是进入contentDraw的一个关键点。下面就对这个函数进行分析说明：
newRenderer->setAnimatableStyle(style.release())
通过注释我们可以先有个简单的了解： setAnimatableStyle() can depend on renderer() already being set.
进入函数之后，发现都会进行setStyle的操作。

setStyle的处理是比较复杂的。这边的主要处理有这样两步：
    1. 保存了一个RenderStyle的指针： m_style = style;
    2. 指向了一个RenderObject: styleDidChange(diff, oldStyle.get());

styleDidChange是一个虚函数，而RenderObject是Render树的一个根节点，所以在下面的很多子类中都有具体的实现。
比如：RenderText，RenderBox，RenderInline，RenderImage等~

这个堆栈再往后就是一些render方面比较深的操作了，比如renderlayer，renderbox等，这些将在接下来进行研究

猿氏悟语
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 2
    评论
专栏目录
ICC2：解决transition的利器——add_buffer_on_route
m0_61544122的博客
05-22 2254
ICC2 add_buffer_on_route修transition
添加IO buffer的作用
hepiaopiao_wemedia的博客
11-26 3900
IO buffer： 使用方法：attachIOBuffer 主要是指放置在block level的port附近的buffer，可以起到增强port的吸引力的作用，提高一下port的驱动能力，防止block外面的wire太长，而使得计算delay不准。 IO buffer只加在input port上，不加在output port上。 防止工具出现不能精确计算的情况；怕漏掉constrain...
数字后端基本概念介绍＜IO Buffer＞
IC后端小白的博客
08-27 3205
今天要介绍的数字后端概念是IO Buffer。主要是指放置在block level的port附近的buffer，可以起到增强port的吸引力的作用， 提高一下驱动port的驱动能力，防止block外面wire太长，而使得计算delay不准。 使用方法 attachIOBuffer  attachIOBuffer -baseName iobuffer -in bufx4 ...
Innovus
m0_57142417的博客
09-15 5390
指定global route和detail route的上下限 setDesignMode -topRoutingLayer -bottomRoutingLayer N12 工艺pr工具避免P48 layer拐角的问题 addRoutingHalo -lithoHalo -cell
Mina源码阅读笔记（二）- IoBuffer的封装
cruise技术博客
11-07 3276
在阅读IoBuffer源码之前，我们先看Mina对IoBuffer的描述：A byte buffer used by MINA applications. This is a replacement for ByteBuffer. 这是一个对ByteBuffer的replacement，同样是用作缓冲区，做内容的切换和承载的容器，为什么要用重新封装ByteBuffer，MINA是这么给出解释的
Android WebKit HTML主资源加载过程
04-06
Android WebKit HTML主资源加载过程
WebKit加载网页的流程.pdf
04-09
WebKit加载网页的流程
Webkit_webkit浏览器_webkit_android_
10-01
基于Webkit的新手级浏览器源码是一个简易web浏览器，基于安卓Webkit开发的。
Android Webkit
11-28
关于 Android Webkit的一些原理性应用
数字后端基本概念
XPhp95的博客
11-20 1万+
转载：Tao_ZT 链接：https://blog.csdn.net/Tao_ZT/article/details/102456649 数字后端基本概念macroBox坐标方向standard cellEndCapWelltapblack boxrowtrackFillerDecapGridLitho GridFinFET GridBlockagePlacement Blockage图形界面Routing BlockagePinBlockagekeep out marginsize blockagemode
IO缓冲区的原理和使用
cainiaoheng的博客
06-25 3894
缓冲区就是内存里的一块区域，把数据先存内存里，然后一次性写入，类似于数据库的批量操作，这样大大提高高了数据的读写速率。 现在的外设控制器都有自己的缓冲池，如磁盘和网卡，通过缓冲IO的方式读取时，如BufferedInputStream里就有个buf块，CPU可把外设里的缓冲池available的字节块整块读入该buf内存。 以下是分别是利用缓冲区进行读写和复制操作的使用代码 import
Iobuffer的使用
weixin_30887919的博客
03-29 1327
写模式: 创建Iobuffer实例，使用Iobuffer的static方法-allocate，有一个参数的方法或者两个参数，第一个参数capacity是指定创建的Iobuffer的容量的最大值，需要注意的是，首先capacity不能小于0，其次java并不是一次性就分配给该Iobuffer这么大的空间，而是根据缓冲区存储数据的实际情况动态分配。第二个参数direct是指定使用直接缓冲区还是j...
阻塞IO和NIO学习心得
周鹏飞的IT学习之路
03-20 164
阻塞IO和NIO学习心得 阻塞IO和NIO学习心得阻塞IO和NIO学习心得1.阻塞IO的问题在哪？2.NIO（New IO）2.1. 概述2.2. Channel2.3. Buffer2.4. Selector3. Buffer缓冲3.1. 四个属性含义3.2. Buffer的常见方法3.3. 缓冲区存取数据流程（分配、写、转换、读、清空）4. Channel 通道4.1. FileChannel...
数字后端基本概念介绍<IO Buffer>
Tao_ZT的博客
08-25 2125
今天要介绍的数字后端概念是IO Buffer。主要是指放置在block level的port附近的buffer，可以起到增强port的吸引力的作用， 提高一下驱动port...
时序约束优先级_静态时序分析圣经翻译计划——附录A：SDC
weixin_34378978的博客
01-09 1381
本附录将介绍1.7版本的SDC格式，此格式主要用于指定设计的时序约束。它不包含任何特定工具的命令，例如链接（link）和编译（compile）。它是一个文本文件，可以手写或由程序创建，并由程序读取。某些SDC命令仅适用于实现（implementation）或综合（synthesis），但是本附录会列出所有SDC命令。SDC语法是基于TCL的格式，即所有命令都遵循TCL语法。一个SDC文件会在文件...
Chromium网页光栅化过程分析
热门推荐
老罗的Android之旅
05-23 2万+
在前面一篇文章中，我们分析了网页CC Layer Tree同步为CC Pending Layer Tree的过程。同步操作完成后，CC Pending Layer Tree中的每一个Layer都会被划分成一系列的分块，并且每一个分块都会被赋予一个优先级。接下来CC模块会根据优先级对分块进行排序。优先级越高的分块越排在前面，越排在前面的分块就越快得到光栅化。本文接下来就详细分析网页分块的光栅化过程。
chromium for android硬件渲染流程全解析(render进程)
jaylinzhou的专栏
01-15 8079
这篇博客分析的是网页内容更新时(比如滚动)，render进程将新的网页内容渲染出来的完整流程。 我把Render进程的整个处理流程分成四个大的子流程： 一.发生在主线程中，网页内容绘制命令被存储在LayerTreeHostImpl包含的LayerTreeImpl中。 二.发生在实现线程中，网页内容的光栅化，及光栅化后，变为像素的网页内容被作为纹理数据上传给opengles.(glTexIma
webkit中 Frame对象分析
Richard的专栏
04-07 1193
<br /><br />webkit中 Frame对象分析<br />Frame应该是整个webcore里面最核心的对象之一,前面在讲Page对象的文章中，也提到过，从Page的角度来看，其实一个Page就是由一个或者多个Frame构成，而这些Frame是以树状的关系组织，我们来看一段HTML代码<br /> view plaincopy to clipboardprint?<html>    <body>      hello, everyone!       <iframe src="..."/>   
WebKit研究
C++与Web
01-31 2264
js执行研究 js代码文本执行前的获取 bool ScriptLoader::prepareScript(const TextPosition& scriptStartPosition, LegacyTypeSupport supportLegacyTypes) { ... ... ... executeScript(ScriptSourceCode(scriptContent(), scr
androidx.webkit:webkit 加载pdf
最新发布
05-16
在 WebView 的加载过程中，androidx.webkit:webkit 库会将 PDF 文件渲染为可交互的页面，并提供导航和其他功能，以便用户可以轻松浏览和操作文件。 需要注意的是，加载 PDF 文件需要有相应的浏览器插件或支持库。在...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值