![]() Install Ageđ5341 seconds (4.3 hours) since version was first installed.ĬPU Info GenuineIntel family 6 model 15 stepping 11Ħ xul.dll CrashReporter::CreatePairedMinidumps toolkit/crashreporter/nsExceptionHandler.cpp:1707ħ xul.dll mozilla::plugins::PluginModuleParent::ShouldContinueFromReplyTimeout dom/plugins/PluginModuleParent.cpp:226Ĩ xul.dll mozilla::ipc::SyncChannel::ShouldContinueFromTimeout ipc/glue/SyncChannel.cpp:261ĩ xul.dll mozilla::ipc::RPCChannel::Call ipc/glue/RPCChannel.cpp:210ġ0 xul.dll mozilla::plugins::PPluginScriptableObjectParent::CallInvokeDefault obj-firefox/ipc/ipdl/PPluginScriptableObjectParent.cpp:367ġ1 xul.dll mozilla::plugins::PluginScriptableObjectParent::ScriptableInvokeDefault dom/plugins/PluginScriptableObjectParent.cpp:265ġ2 xul.dll CallNPMethodInternal modules/plugin/base/src/nsJSNPRuntime.cpp:1512ġ3 xul.dll NPObjWrapper_Call modules/plugin/base/src/nsJSNPRuntime.cpp:1747ġ4 js3250.dll js_Invoke js/src/jsinterp.cpp:1360ġ5 js3250.dll js_Interpret js/src/jsops.cpp:2240ġ6 js3250.dll js_Invoke js/src/jsinterp.cpp:1368ġ7 xul.dll nsXPCWrappedJSClass::CallMethod js/src/xpconnect/src/xpcwrappedjsclass.cpp:1696ġ8 xul.dll nsXPCWrappedJS::CallMethod js/src/xpconnect/src/xpcwrappedjs.cpp:570ġ9 xul.dll PrepareAndDispatch xpcom/reflect/xptcall/src/md/win32/xptcstubs.cpp:114Ģ0 xul.dll SharedStub xpcom/reflect/xptcall/src/md/win32/xptcstubs.cpp:141Ģ1 xul.dll nsDOMEventListenerWrapper::HandleEvent content/events/src/nsDOMEventTargetHelper.cpp:65Ģ2 xul.dll nsEventListenerManager::HandleEventSubType content/events/src/nsEventListenerManager.cpp:1041 Signature hang | mozilla::plugins::PPluginScriptableObjectParent::CallInvokeDefault(nsTArray const&, mozilla::plugins::Variant*, bool*) Before we split plugins out of process, the stack trace that a plugin dev would have seen would have contained these browser frames and they can be helpful to plugin devs too. In order to recognize cases where the browser has done something "problematic", we send a report containing what the browser was doing. Let me know if you need more, and thank you for your support.įwiw, the reason you're seeing two reports is that what's happening is the browser process asks the plugin process to do something, the plugin process doesn't respond w/in a "reasonable time period", and we kill the plugin. ![]() No surprise here I think because each crash was related to the npctrl.dll. I couldn't produce a crash and also receive no error messages from the SL runtime anymore. Please note that for the third ones I was first redirected to. Here are the three last ones from last night. ![]() All working in 3.6.3ġ.) No, when the Plug-In crashes, there are no errors in the console.Ģ.) Every crash seems to produce two entries in the crash list (at least there are always two with very close/similar timestamps). Some developing related addons (Dev Toolbar, Firebug etc.). Plug-in crashes, deserialization errors in SL4 (filed several reports).ĭefault theme. No public demo of the problem yet, unfortunately. Default Visual Studio sample (without customization) works. Seems to be related to a certain constellation of SL4/RIA Services. Network messages inspected and proofed valid in Fiddler2.Īpplication continues to work without any problems in IE8 and Firefox 3.6.3.ġ. Error seems to be related to deserialization of network messages in Silverlight (complains about bad formatting, wrong data types etc.). ![]() Silverlight 4 WCF/RIA Services Application, built with the default Visual Studio 2010 Business Template and customized (unfortunately no public demo yet).Ĭalling WCF/RIA service methods leads to random error messages on the client side (= Silverlight Host), and to plug-in crashes in ~25% of the attempts.
0 Comments
Leave a Reply. |