terrypin Posted September 3, 2012 Report Share Posted September 3, 2012 I'm again having a spate of those scenarios we've discussed several times before, and wonder if there has been anything new on this issue? I'm talking about the scenario when during the execution of a macro, not only does Forrest freeze and refuse to be removed by any of the regular methods, but the whole system slows down to glacial speeds. It's taking me a couple of minutes from that stage to then close ME Pro via the XP Task Manager. Each operation is taking around 10-15 seconds. Yet no significant CPU resource is being used and nothing else is happening. The current macro in which this problem arises contains a series of Macro Run commands. And each of the individual sub-macros runs OK on its own. The structure looks like this: Macro Run: MacroA Window Activate: %tFolderName% Wait for Window Title: %tFolderName% Macro Run: MacroB Window Activate: %tFolderName% Wait for Window Title: %tFolderName% Macro Run: MacroC Window Activate: %tFolderName% Wait for Window Title: %tFolderName% etc The sub-macros are not exactly the same. The later ones have a few TextType PgDown commands. I think it's when the main macro encounters these later sub-macros that the issue arises. Any thoughts from anyone (hey, maybe even Insight!) would be appreciated please. -- Terry, East Grinstead, UK Quote Link to comment Share on other sites More sharing options...
Cory Posted September 3, 2012 Report Share Posted September 3, 2012 I recently submitted a new bugrep on a problem like this. On a new W7-64 laptop with Office 2010 the machine would occasionally experience what I call "Molasses". 0% CPU, 23% memory and yet every user input is delayed anywhere from a couple of seconds to a minute. Killing MacExp.exe and MEProx64.exe instantly restores the normal responsiveness. It seems that if the system is rebooted the problem takes many hours before it reappears. But if MEP is simply restarted it occurs in a few minutes. ISS is working on this but it would be good if you continued to report your experiences to them. Additionally on my desktop machine which is much slower I've experienced something like molasses but not as paralyzing. Everything becomes notchy and slow to respond. EG typing will result in no characters echoed then suddenly a burst of characters. Opening Task Manager or doing anything in the system seem laggy but now as bad as the aforementioned. Killing MEP and the MEProx64 seems to restore responsiveness but it's hard to tell for certain. Might be a coincidence. I plan on creating a batch file with two TaskKill commands for the user to aid in a speedy recovery because as you pointed out just opening the Task Manger and killing the task takes several minutes. Quote Link to comment Share on other sites More sharing options...
terrypin Posted September 3, 2012 Author Report Share Posted September 3, 2012 Thanks Cory. I submitted at least one report on this maybe a year or two ago, with no feedback or apparent action. Maybe you'll be more successful. -- Terry, East Grinstead, UK Quote Link to comment Share on other sites More sharing options...
acantor Posted September 4, 2012 Report Share Posted September 4, 2012 I have never reported it as a bug, but it happens to me occasionally. Certain combinations of commands seem to be the trigger, something like this: Move Mouse Pointer to 100, 100 Repeat Start 10 times If Mouse Pointer = arrow Exit Repeat Else Delay 200 ms End if Repeat End Quote Link to comment Share on other sites More sharing options...
paul Posted September 5, 2012 Report Share Posted September 5, 2012 I have attached an executable you might find useful - it terminates MEP using the context menu of the tray icon, then restarts it. This assumes that MEP is located at C:\Program Files (x86)\Macro Express Pro\MacExp.exe. For those of you with AutoIt, I include the source code. #NoTrayIcon #Include <GuiToolBar.au3> Dim $hSysTray_Handle, $iSystray_ButtonNumber $iSystray_ButtonNumber = Get_Systray_Index("Macro Express Pro") If $iSystray_ButtonNumber <> -1 Then Sleep(1000) _GUICtrlToolbar_ClickButton($hSysTray_Handle, $iSystray_ButtonNumber, "right") Sleep(500) Send("t") EndIf Sleep(1000) ShellExecute("C:\Program Files (x86)\Macro Express Pro\MacExp.exe") Func Get_Systray_Index($sToolTipTitle) $hSysTray_Handle = ControlGetHandle('[Class:Shell_TrayWnd]', '', '[Class:ToolbarWindow32;Instance:1]') If @error Then MsgBox(16, "Error", "System tray not found") Exit EndIf Local $iSystray_ButCount = _GUICtrlToolbar_ButtonCount($hSysTray_Handle) If $iSystray_ButCount = 0 Then MsgBox(16, "Error", "No items found in system tray") Exit EndIf For $iSystray_ButtonNumber = 0 To $iSystray_ButCount If StringInStr(_GUICtrlToolbar_GetButtonText($hSysTray_Handle, $iSystray_ButtonNumber), $sToolTipTitle) <> 0 Then Return $iSystray_ButtonNumber EndIf Next Return -1 EndFunc RestartMacroExpress.zip Quote Link to comment Share on other sites More sharing options...
terrypin Posted September 5, 2012 Author Report Share Posted September 5, 2012 Thanks Paul, that should prove very handy. When I tried to run RestartMacroExpress.exe I got this: I did install AutoIt! ages ago (following your recommendation here at the time) but never spent enough time to get going in earnest. But I've managed to modify your script to reflect my ME Pro being located here: C:\Program Files\Macro Express Pro\MacExp.exe And after re-saving it with extension .au3 and d-clicking it, it worked perfectly. Presumably doing so in a freeze situation will be more tricky and much slower, but it should be a lot better than what I've been doing. Ive now compiled it and I'm considering where best to locate it, for easiest use in a freeze. Later this evening I'll try testing my freeze-making macro again, use the restart program, and report back. -- Terry, East Grinstead, UK Quote Link to comment Share on other sites More sharing options...
paul Posted September 6, 2012 Report Share Posted September 6, 2012 Remind me - what OS are you running? x86 or x64? Quote Link to comment Share on other sites More sharing options...
terrypin Posted September 6, 2012 Author Report Share Posted September 6, 2012 Remind me - what OS are you running? x86 or x64? X86 -- Terry, East Grinstead, UK Quote Link to comment Share on other sites More sharing options...
terrypin Posted September 6, 2012 Author Report Share Posted September 6, 2012 Later this evening I'll try testing my freeze-making macro again, use the restart program, and report back. Unfortunately, although it worked fine under normal conditions, during the freeze it didn't. I was unable to take a screenshot but it was if the script had right clicked the toolbar and then clicked Toolbars Rather like this, except that the Toolbars menu was almost alongside the other: Had to resort to TM. -- Terry, East Grinstead, UK Quote Link to comment Share on other sites More sharing options...
Cory Posted September 6, 2012 Report Share Posted September 6, 2012 Task kill is much simpler. Just look online for the syntax. Also when molasses occurs closing by way of the tray will result in the icon vanishing but the processes will still be running invisibility. Quote Link to comment Share on other sites More sharing options...
terrypin Posted September 6, 2012 Author Report Share Posted September 6, 2012 Looks unduly complicated! An example would be good. What syntax do you use to kill ME Pro on your own local PC? http://ss64.com/nt/taskkill.html Terry, UK Quote Link to comment Share on other sites More sharing options...
Cory Posted September 19, 2012 Report Share Posted September 19, 2012 I suppose unduly complicated would depend on your skill level. Here's my batch file: taskkill /im macexp.exe /f taskkill /im meprox64.exe /f pause Quote Link to comment Share on other sites More sharing options...
terrypin Posted September 19, 2012 Author Report Share Posted September 19, 2012 Thanks, I'll try that when I get my next freeze. -- Terry, East Grinstead, UK Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.