Home Forums DITA and XMetaL Discussion Upgrade to 6.0 — map editor crash? Reply To: Upgrade to 6.0 — map editor crash?

gcrews

Reply to: Upgrade to 6.0 — map editor crash?

I'm glad you were able to reproduce the issue on your side.
Thanks for all the help trying to debug this issue.

Additional information:
We have  4 other writers extensively using XMetaL 5.5 during the day with the same McAfee version, settings, and policies with no issues. There must have been something changed in XMetaL 6 that  introduced this issue.

The host system I ran my VM test on was an Intel q6600 with VT-x,  witch may attributive to it crashing on  my test vm and not on your side.

Here is the last stack trace after a crash: ( you can probably get this info now)
Faulting application xmetal60.exe, version 6.0.0.122
faulting module oleaut32.dll, version 5.1.2600.5512
fault address 0x00004942.
[email protected]()  + 0x52 bytes
jscript.dll!VAR::Clear()  + 0x47 bytes
jscript.dll!GcAlloc::ReclaimGarbage()  + 0x77 bytes
jscript.dll!GcContext::Reclaim()  + 0x17e bytes
jscript.dll!GcContext::Collect()  – 0x225 bytes
jscript.dll!CScriptRuntime::Run()  – 0x6368 bytes
jscript.dll!ScrFncObj::Call()  + 0x85 bytes
jscript.dll!NameTbl::InvokeInternal()  + 0x5a95 bytes
jscript.dll!VAR::InvokeByDispID()  + 0x1f7d bytes
jscript.dll!CScriptRuntime::Run()  + 0x5592 bytes
jscript.dll!ScrFncObj::Call()  + 0x85 bytes
jscript.dll!NameTbl::InvokeInternal()  + 0x6b bytes
jscript.dll!VAR::InvokeByDispID()  + 0x1f7d bytes
jscript.dll!VAR::InvokeByName()  + 0x6566 bytes
jscript.dll!VAR::InvokeDispName()  + 0x40 bytes
jscript.dll!VAR::InvokeByDispID()  + 0x54 bytes
jscript.dll!CScriptRuntime::Run()  – 0x1c65 bytes
jscript.dll!ScrFncObj::Call()  + 0x85 bytes
jscript.dll!NameTbl::InvokeInternal()  + 0x6b bytes
jscript.dll!VAR::InvokeByDispID()  + 0x1f7d bytes
jscript.dll!VAR::InvokeByName()  + 0x6566 bytes
jscript.dll!VAR::InvokeDispName()  + 0x40 bytes
jscript.dll!VAR::InvokeByDispID()  + 0x54 bytes
jscript.dll!CScriptRuntime::Run()  – 0x1c65 bytes
jscript.dll!ScrFncObj::Call()  + 0x85 bytes
jscript.dll!NameTbl::InvokeInternal()  + 0x6b bytes
jscript.dll!VAR::InvokeByDispID()  + 0x1f7d bytes
jscript.dll!VAR::InvokeByName()  + 0x6566 bytes
jscript.dll!VAR::InvokeDispName()  + 0x40 bytes
jscript.dll!VAR::InvokeByDispID()  + 0x54 bytes
jscript.dll!CScriptRuntime::Run()  + 0x5592 bytes
jscript.dll!ScrFncObj::Call()  + 0x85 bytes
jscript.dll!CSession::Execute()  – 0x398 bytes
jscript.dll!COleScript::ExecutePendingScripts()  + 0x141 bytes
jscript.dll!COleScript::ParseScriptTextCore()  + 0x1a6 bytes
jscript.dll!COleScript::ParseScriptText()  + 0x2b bytes
xmetal60.exe!00a16f32()
[Frames below may be incorrect and/or missing, no symbols loaded for xmetal60.exe]

Here is a hack I came up with: (reset the WHS reg keys, open XMetaL, set WHS keys back)
As long as you don't open Iexplorere or Outlook during the time the keys are changed and you don't surf the web in in the preview pane after clinking a link in a document I don't think there is much of a security risk.

REGEDIT.EXE /S “%~dp0reg.reg”
rem reg.reg
rem Windows Registry Editor Version 5.00
rem [HKEY_CLASSES_ROOTCLSID{f414c260-6ac0-11cf-b6d1-00aa00bbbb58}InprocServer32]
rem @=”C:\WINDOWS\system32\JScript.dll”
rem [HKEY_CLASSES_ROOTCLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}InprocServer32]
rem @=”C:\WINDOWS\system32\VBScript.dll”

start “XMetaL” /B “C:Program FilesXMetaL 6.0Authorxmetal60.exe”
PING 1.1.1.1 -n 1 -w 20000
REGEDIT.EXE /S “%~dp0mc.reg”
rem mc.reg
rem Windows Registry Editor Version 5.00
rem [HKEY_CLASSES_ROOTCLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}InprocServer32]
rem @=”C:\Program Files\McAfee\VirusScan Enterprise\scriptsn.dll”
rem [HKEY_CLASSES_ROOTCLSID{f414c260-6ac0-11cf-b6d1-00aa00bbbb58}InprocServer32]
rem @=”C:\Program Files\McAfee\VirusScan Enterprise\scriptsn.dll”

Reply

Products
Downloads
Support