Secunia CSI7
Advisories
Research
Forums
Create Profile
Our Commitment
PSI
PSI API
CSI
OSI
xSI
Vulnerabilities
Programs
Open Discussions
My Threads
Create Thread
Statistics
About

Forum Thread: build 8013 crash on startup, stack trace provided

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
PSI

This thread has been marked as locked.
bvoigt build 8013 crash on startup, stack trace provided
Member 29th Oct, 2013 00:26
Ranking: 0
Posts: 2
User Since: 29th Oct, 2013
System Score: N/A
Location: US
On Windows 8.1 x64, build 8013 crashes on startup with an access violation.

Using the Microsoft public symbol servers I was able to capture the following stack trace:

It looks like the PSI javascript might be calling a "getBoundingClientRect" function before the page is fully loaded/rendered.

the faulting line is

cmp dword ptr [esi+14h],eax

but ESI is zero (null pointer)

> mshtml.dll!CFlowLayout::CalcSizeCoreCSS1Strict() + 0x351532 bytes
mshtml.dll!CFlowLayout::CalcSizeCore() + 0x1c562 bytes
mshtml.dll!CFlowLayout::CalcSizeVirtual() + 0x63 bytes
mshtml.dll!CLayout::CalcSize() + 0x2bf bytes
mshtml.dll!CFlowLayout::MeasureSite() + 0x3f0 bytes
mshtml.dll!CFlowLayout::GetSiteWidth() + 0xc8 bytes
mshtml.dll!CLSMeasurer::GetSiteWidth() + 0x56 bytes
mshtml.dll!CEmbeddedILSObj::Fmt() + 0x1f4 bytes
msls31.dll!_ProcessOneRun@24() + 0x2bf bytes
msls31.dll!_FetchAppendEscCore@36() + 0xd3 bytes
msls31.dll!_FinishSublineCore@4() - 0x7ec4 bytes
msls31.dll!_LsCreateLine@40() + 0x1de1 bytes
msls31.dll!_LsCreateLine@40() + 0xc5 bytes
mshtml.dll!CLSMeasurer::LSDoCreateLine() + 0x170 bytes
mshtml.dll!CLSMeasurer::LSMeasure() + 0x47 bytes
mshtml.dll!CLSMeasurer::Measure() + 0x126 bytes
mshtml.dll!CRecalcLinePtr::MeasureLine() + 0x1f9 bytes
mshtml.dll!CDisplay::RecalcLines() + 0x56a bytes
mshtml.dll!CDisplay::UpdateView() + 0x17c bytes
mshtml.dll!CFlowLayout::CommitChanges() + 0xd548 bytes
mshtml.dll!CDisplay::WaitForRecalc() + 0x5f71d bytes
mshtml.dll!CFlowLayout::Notify() + 0x29f58 bytes
mshtml.dll!NotifyElement() + 0x30655c bytes
mshtml.dll!NotifyAncestors() + 0x92b17 bytes
mshtml.dll!CMarkup::Notify() + 0x168 bytes
mshtml.dll!CElement::SendNotification() + 0x5f bytes
mshtml.dll!CElement::EnsureRecalcNotify() - 0x1736c6 bytes
mshtml.dll!CElement::GetBoundingClientRectHelper( ) + 0x4b bytes
mshtml.dll!CElement::getBoundingClientRect() + 0x79 bytes
mshtml.dll!Method_IDispatchpp_void() + 0x28 bytes
mshtml.dll!CBase::ContextInvokeEx() + 0x2b6 bytes
mshtml.dll!CElement::ContextInvokeEx() + 0x4c bytes
mshtml.dll!CInput::VersionedInvokeEx() + 0x2e bytes
mshtml.dll!CBase::PrivateInvokeEx() + 0x75 bytes
jscript9.dll!HostDispatch::CallInvokeEx() + 0xb2 bytes
jscript9.dll!HostDispatch::InvokeMarshaled() + 0x4b bytes
jscript9.dll!HostDispatch::InvokeByDispId() + 0x1cf bytes
jscript9.dll!DispMemberProxy::DefaultInvoke() + 0x27 bytes
jscript9.dll!Js::InterpreterStackFrame::Process() + 0x66f bytes
jscript9.dll!Js::InterpreterStackFrame::Interpret erThunk<1>() + 0x1e8 bytes
05811d39()
jscript9.dll!Js::InterpreterStackFrame::Process() + 0x825 bytes
jscript9.dll!Js::InterpreterStackFrame::Interpret erThunk<1>() + 0x1e8 bytes
05811d41()
jscript9.dll!Js::JavascriptFunction::EntryApply() + 0x264 bytes
jscript9.dll!Js::InterpreterStackFrame::Process() + 0x66f bytes
jscript9.dll!Js::InterpreterStackFrame::Interpret erThunk<1>() + 0x1e8 bytes
05811d51()
jscript9.dll!Js::JavascriptFunction::EntryApply() + 0x264 bytes
jscript9.dll!Js::InterpreterStackFrame::Process() + 0x66f bytes
jscript9.dll!BailOutRecord::BailOutHelper() + 0x191 bytes
jscript9.dll!BailOutRecord::BailOutCommonNoCodeGe n() + 0x47 bytes
jscript9.dll!BailOutRecord::BailOutCommon() + 0x1e bytes
jscript9.dll!BailOutRecord::BailOut() + 0x33 bytes
090206e0()
jscript9.dll!Js::JavascriptFunction::EntryApply() + 0x264 bytes
jscript9.dll!Js::InterpreterStackFrame::Process() + 0x825 bytes
jscript9.dll!Js::InterpreterStackFrame::Interpret erThunk<1>() + 0x1e8 bytes
05811d59()
jscript9.dll!Js::InterpreterStackFrame::Process() + 0x825 bytes
jscript9.dll!Js::InterpreterStackFrame::Interpret erThunk<1>() + 0x1e8 bytes
05811d69()
jscript9.dll!Js::JavascriptFunction::EntryApply() + 0x264 bytes
jscript9.dll!Js::InterpreterStackFrame::Process() + 0x66f bytes
jscript9.dll!Js::InterpreterStackFrame::Interpret erThunk<1>() + 0x1e8 bytes
05811d71()
jscript9.dll!Js::JavascriptFunction::CallFunction <1>() + 0x81 bytes
jscript9.dll!Js::JavascriptFunction::CallRootFunc tion() + 0x97 bytes
jscript9.dll!ScriptSite::CallRootFunction() + 0x46 bytes
jscript9.dll!ScriptSite::Execute() + 0x6c bytes
jscript9.dll!JavascriptDispatch::InvokeOnSelf() + 0xcc bytes
jscript9.dll!JavascriptDispatch::InvokeEx() + 0x189 bytes
jscript9.dll!JavascriptDispatch::Invoke() + 0x36 bytes
mshtml.dll!CWindow::ExecuteCallbackScript() + 0xa5 bytes
mshtml.dll!CWindow::FireTimeOut() + 0x1b4 bytes
mshtml.dll!CPaintBeat::ProcessTimers() + 0x1de bytes
mshtml.dll!CPaintBeat::OnWMTimer() + 0x3b bytes
mshtml.dll!FormsOnTimer() + 0x69 bytes
mshtml.dll!GlobalWndProc() + 0x1714e bytes
user32.dll!__InternalCallWinProc@20() + 0x23 bytes
user32.dll!_UserCallWinProcCheckWow@36() + 0x1a4 bytes
user32.dll!_DispatchMessageWorker@8() + 0x200 bytes
user32.dll!_DispatchMessageW@4() + 0x10 bytes
psi.exe!010daca5()
[Frames below may be incorrect and/or missing, no symbols loaded for psi.exe]
psi.exe!010daeae()
psi.exe!010dad0a()
psi.exe!010dc548()
kernel32.dll!7689495d()
ntdll.dll!773b98ee()
ntdll.dll!773b98c4()

TonyB. RE: build 8013 crash on startup, stack trace provided
Member 1st Nov, 2013 15:23
Score: -34
Posts: 38
User Since: 1st Nov 2013
System Score: N/A
Location: US
dose it here as well i had to go back to version 2.0 to make it work.
Was this reply relevant?
+0
-0
bvoigt RE: build 8013 crash on startup, stack trace provided
Member 1st Nov, 2013 16:08
Score: 0
Posts: 2
User Since: 29th Oct 2013
System Score: N/A
Location: US
Yes, now that I saw Secunia officially say that 2.x still receives the latest patch information and is recommended for power users, I've switched to it as well. I like 2.x's GUI much much better anyway. The only reason I updated to 3.0 to begin with was because I assumed 2.x was EOL once a newer version was released.
Was this reply relevant?
+0
-0

This thread has been marked as locked.


 Products Solutions Customers Partner Resources Company
 
 Corporate
Vulnerability Intelligence Manager (VIM)
Corporate Software Inspector (CSI)
Consumer
Personal Software Inspector (PSI)
Online Software Inspector (OSI)
 Industry
Compliance
Technology
Integration
 Customers
Testimonials
 VARS
MSSP
Technology Partners
References
 Reports
Webinars
Events
 About us
Careers
Memberships
Newsroom


 
© 2002-2014 Secunia ApS - Rued Langgaards Vej 8, 4th floor, DK-2300 Copenhagen, Denmark - +45 7020 5144
Terms & Conditions and Copyright - Privacy - Report Vulnerability