That lowered my physical memory consumption to 32%, and then I could insert any pictures I wanted, no matter how big. If.I disconnected from the Internet and closed the three biggest eaters of memory: Kaspersky, Malwarebytes, and Dropbox. You might be running an old or incompatible version of Word on your Mac.
Office 2016 Zing Mac OS X IsWord is apparently just as big a memory glutton as the other three programs, all of which I really need running. Users often have to face a situation like this when Microsoft Word, Excel, Outlook, PowerPoint, and other MS office tools stop responding.The problem, then, is competition for resources, not something going on with Word. Even though Mac OS X is a reliable OS, but this doesn’t make it glitch free.When memory gets overused, things just stop working (e.g., Word), despite there being a ton of space for paging on the new device. Win 10 is not using any of that space. I connected an external hard disk drive with 1 TB of space and added it to the list of locations for page file/virtual memory. This is probably now an issue for another forum, but I'll describe it here. By contrast, Office on the Mac still has the menus, and you can give a fair. Freezing and splitting the window and recording and running macros.It does appear, though, that the problem is with Websense Endpoint, which I didn't even know I had on my PC.As long as I can toggle MBAE on and off when necessary, I'll wait for MB to release their "new mechanism."Thanks for all your help. We are working on a new mechanism to handle these types of conflicts.Further experimentation proved that if I simply turn off Anti-Exploit (MBAE) instead of all of MB, Word works perfectly. If you are experiencing this issue please contact Websense to report this bug to them ("bad attempt to copy jmp qword instruction rip based"). However due to a bug in Websense's hooking mechanism it improperly handles the hook and may create crashes when opening Word, Excel or other applications. Not wanting to exist without the protection that I get from MB, I read further.Websense Endpoint hooks KernelBase!LoadLibraryExW API via QIPCAP64.DLL. I disabled Malwarebytes, and the problem went away.
0 Comments
Leave a Reply. |
Details
AuthorMary ArchivesCategories |