Html control - after last Windows Update crashes Autocad application sometimes.
For exapmle it happens if run OPENDCLDEMO->"HTML Example" then browse to www.google.com (or other but http://www.opendcl.com - it seems this depends on page contents) and press "Close" button, e.g. if calling dcl-Form-Close when some "wrong made" page is loaded.
Autocad also crashes when I navigate to some *.htm file save on harddisk (but only if I do it before browsing to some internet URL) or when calling dcl-Html-UpdateHtmlCode (on non-modal form).
Windows 7 x64 Autocad 2011, 2013
Apologies, if its not my place to butt in to this bug report. But just in case it helps resolution of this bug.
I had a similar problem with dcl_html_GetHtmlDocument suddenly failing on modeless forms after the last Windows update (after years of being fine). Changing the Event Invoke of the controls from asynchronous to synchronous fixed it for me.
I am able to reproduce the problem. The crash occurs in mshtml.dll, which is the code for the Windows web browser control. I cannot tell what it is doing, however the executing code at the point of exception is in a tight loop that indexes over an array and obviously past the end of the array until it reaches the end of the stack and crashes. Unfortunately this does not appear to be something I can address in the OpenDCL code.
Changing the Event Invoke of the contols from asynchronous to synchronous also fixed it for me. Crashes seems to be gone if all these methods are not called from ANY asynchronous event on modeless forms or from autocad's command line or other lisp code.
I'm having the same issue when I try to close a form with an HTML control on it. The prob. is it's a Modal form, so I can't change it to synchronous ;-(
I guess I can convert the form to modeless....
I have this same problem and its critical to solve it. I noticed it happend after updateing to Internet Explorer 11. I removed windows update for IE and html control works again. Owen , I hope it helps to solve this issue.
Thx
Mateusz
See also this thread on the forum:
http://www.opendcl.com/forum/index.php?topic=2172.0
As noted, the problem was introduced with the KB2962872 update:
http://support.microsoft.com/kb/2962872