【问题标题】:ThreeJS : IE11 crashes on Render();ThreeJS:IE11 在 Render() 上崩溃;
【发布时间】:2014-04-16 06:05:35
【问题描述】:

我在使用 WebGL 编程时遇到了一些奇怪的 Internet Explorer 11 问题。我在所有浏览器中都运行良好,但是当我改变 4 个网格的位置时突然... IE 决定崩溃(在调试模式下,不指向代码中的任何特定内容)。

我正在运行 IE 11

GL 版本 - WebGL 0.93

着色语言版本 - WebGL GLSL ES 0.93

我收到以下错误: iexplore.exe 中 0x03F6435B (mshtml.dll) 处的未处理异常:0xC0000005:访问冲突写入位置 0xBF35051C。

(最后 5 个)调用堆栈:

mshtml.dll!CMarkupPointer::RemoveMeFromList(void) 未知 mshtml.dll!CBackgroundInfo::Property<class CBackgroundImage>(int)'::7'::`'fieldDefaultValue'(void) 的动态 atexit 析构函数未知 mshtml.dll!CMarkupPointer::MoveToPointer(class CMarkupPointer const *) 未知 mshtml.dll!CDisplayPointer::MoveToPointer(class CDisplayPointer *) 未知 mshtml.dll!CSelectTracker::DoSelection(class CEditEvent *,int,int *) 未知

这是创建网格的代码:

function PrepareFlowArrows(l_vDiffuser) {
    var m_vExtraLoader = new THREE.JSONLoader();
    m_vExtraLoader.load('3D_Control/models/FlowArrow.js', callbackLoadFlowArrows(l_vDiffuser));
}

// Callback function for FlowArrows when loading models
function callbackLoadFlowArrows(l_vDiffuser) {
    return function (geometry) {
        var l_vRotation = 0;
        for (var i = 0; i < 4; i++) {
            if (i == 0)
                l_vRotation = -1.5707; //-1.5707;
            else if (i == 1)
                l_vRotation = 3.1414;//3.1414;
            else if (i == 2)
                l_vRotation = 1.5707;//1.5707;
            else
                l_vRotation = 0;

            var l_vMaterial = new THREE.MeshBasicMaterial();                      // SETTINGS COLORS MANUALLY (way more nicer with textures though)
            l_vMaterial.color.r = 0;
            l_vMaterial.color.g = 255;
            l_vMaterial.color.b = 0;

            var m_vTempFlowArrowMesh = new THREE.Mesh(geometry, l_vMaterial);
            m_vTempFlowArrowMesh.scale.x = m_vTempFlowArrowMesh.scale.y = m_vTempFlowArrowMesh.scale.z *= 25;
            m_vTempFlowArrowMesh.position.set(0, 0, 0);
            m_vTempFlowArrowMesh.rotation.y = l_vRotation;
            l_vDiffuser.AddFlowArrow(m_vTempFlowArrowMesh);
            m_vScene.add(m_vTempFlowArrowMesh);
        }
    }
}

这是在 Render(); 时由于某种原因导致 IE11 崩溃的代码;被调用并且网格被设置为可见。

this.UpdateFlowArrows = function () {
    this.GetBoundingBox();
    if (m_vFlowArrows[0] != null) {
        m_vFlowArrows[0].position.x = m_vBoundingBox.min.x - 100;
        m_vFlowArrows[0].position.y = m_vBoundingBox.min.y + ((m_vBoundingBox.max.y - m_vBoundingBox.min.y) / 2);
        m_vFlowArrows[0].position.z = m_vBoundingBox.min.z + ((m_vBoundingBox.max.z - m_vBoundingBox.min.z) / 2);
        //m_vFlowArrows[0].rotation.y = -1.5707;
    }

    if (m_vFlowArrows[1] != null) {
        m_vFlowArrows[1].position.x = m_vBoundingBox.min.x + ((m_vBoundingBox.max.x - m_vBoundingBox.min.x) / 2);
        m_vFlowArrows[1].position.y = m_vBoundingBox.min.y + ((m_vBoundingBox.max.y - m_vBoundingBox.min.y) / 2);
        m_vFlowArrows[1].position.z = m_vBoundingBox.min.z - 100;
        //m_vFlowArrows[1].rotation.y = 3.1414;
    }

    if (m_vFlowArrows[2] != null) {
        m_vFlowArrows[2].position.x = m_vBoundingBox.max.x + 100;
        m_vFlowArrows[2].position.y = m_vBoundingBox.max.y - ((m_vBoundingBox.max.y - m_vBoundingBox.min.y) / 2);
        m_vFlowArrows[2].position.z = m_vBoundingBox.max.z - ((m_vBoundingBox.max.z - m_vBoundingBox.min.z) / 2);
        //m_vFlowArrows[0].rotation.y = 1.5707;
    }

    if (m_vFlowArrows[3] != null) {
        m_vFlowArrows[3].position.x = m_vBoundingBox.max.x - ((m_vBoundingBox.max.x - m_vBoundingBox.min.x) / 2);
        m_vFlowArrows[3].position.y = m_vBoundingBox.max.y - ((m_vBoundingBox.max.y - m_vBoundingBox.min.y) / 2);
        m_vFlowArrows[3].position.z = m_vBoundingBox.max.z + 100;
        //m_vFlowArrows[3].rotation.y = 1.5707;
    }
}

请注意,此代码在 Chrome、Opera 和 Firefox 中运行良好。我能否以某种方式重写这段代码,以免 IE 崩溃?

编辑 有趣的事情...如果我添加该行

 m_vTempFlowArrowMesh.visible = false;

在callbackLoadFlowArrows中......即使它更新了箭头,它也不会再崩溃了。

【问题讨论】:

    标签: javascript internet-explorer crash three.js webgl


    【解决方案1】:

    IE 团队无法(出于某种尴尬的原因)重现此错误。

    即使我向他们发送了大约 3x800mb 的故障转储文件以及 IE 客户端的信息文件,他们也无法找到问题所在。

    所以...他们关闭了这个问题,因为它在他们眼中不再相关。

    GG 微软。

    叹息

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 1970-01-01
      • 2011-05-10
      • 2018-11-01
      • 1970-01-01
      • 2011-07-24
      • 2011-09-18
      • 2016-06-02
      • 2013-03-14
      相关资源
      最近更新 更多