EVE Online Forum

This is a community forum and not official technical support. — If you need official support: Contact Us

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

DirectX Runtime installer fails to close on completion with EVE installer

Doing either a template (EVE Online) or from scratch Bottle install the following problem occurs:

When running the DirectX runtime installer which is required before EVE is installed, the install will fail to close after it finishes as the next button (Close/Exit) for the installer does not work. The EVE setup wizard will still continue, leaving the DirectX installer running in the background, and at the end of the bottle creation. This is a medium severity bug, as it creates a false positive and may confuse users. I've already tried Force Installer Completion to expedite the install after it acted like it was timing out, but it wasn't actually timing out and if you do a Force Installer Completion the respective shortcuts will not be created. You must wait for the refreshing desktop manager window to come up and let it close the programs then force the bottle to quit to close the DirectX installer. The DirectX runtime appears to remove itself if the install was successful and the shortcuts are created as I cannot find a DirectX subfolder inside of the CCP/EVE/bin location, so using the DirectX redist file from the Microsoft Download Center must be done when a patch fails to install, and should fix further patch false-positives later on.

EVE Installer version is Windows Premium 58188 as recommended by the bottle.

Also, a major memory leak occurs from this issue, I'm using iStatMenus to show real-time memory usage, and it escalated to 3/4 usage and the bottles do not force quit, nor does the application, only killall -9 wineloader will make CrossOver Games close, and the memory is not freed. Only with a logout (Reboot seems to work better) does any of the memory become usable, and there are no resident wine tasks shown by ps auxww or Activity Monitor after logout and killall on wine tasks.

We are aware of the DirectX installation failure and we have fixed it for the next release.

The memory leak sounds like it might be in the Window Server or the graphics drivers. If there are no wine* tasks and you've exited CrossOver Games.app, then there's nothing left of CrossOver that might be using the memory.

See if Activity Monitor shows you which process has a very large Real Memory size (RSIZE).

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi02LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzM5NTcwNzYwLCJjc3JmX3Rva2VuIjoidVo1UEpLQjNDRlRkQWRXeSIsImdkcHIiOjB9