DaDreamWizard

Hanging delays (Win 7, 10)

Hanging delays (Win 7, 10)

I've noticed a couple of similar complaints of Object Dock, slow/hanging & lag. I currently am using Windows 10 but this 'hanging-lag', which comes after launching an app from Object Dock, or attempting to launch an item with Object Dock not responding, like it's writing to itself or something is just not correct.

This lagging started quite a while back with Windows 7 (64bit). I use both a tabbed dock at top of screen and a quick launch dock at screens bottom. Both remain off screen/hidden till the cursor initiates, which is also at times a painful delay or lag.

Sometimes the lag is minimal, yet at times it's painfully long. I thought just maybe it wasn't getting enough cpu priority (above normal) so I even tried upping it's priority with no luck.

If I didn't depend on this menuing system so much I would have left it on the backburner 3 years ago... I noticed people have some Windows 10 issues, yet weirdly enough the lag and delays are somewhat less with Windows 10 then they were with Windows 7, but the lag is still here, and I know because I know how just how fast and snappy Object Dock could be while (over) loaded down with many, many (many!!!!) programs & folders spanning 2 disks.

At first I thought my OS was glitchy (Win 7) till I did a clean fresh install which changed nothing. I wish I recorded exactly when this performance issue started.

Hoping this someday gets resolved. Cause even with everything not being copasetic, I'm still a Stardock fan.

183,684 views 51 replies
Reply #26 Top

Not sure if it's relevant or of any real assistance but when I monitor the internal OD threads using SysInternals' Process Explorer tool I get a CPU activity spike in the following areas during the time that OD is unresponsive (as consistently as I can tell after closing an app that was launched from the dock):

In ObjectDock.exe the thread is called ObjectDock.exe!DotNetCallback+0x35b90 - it spikes from ~0.01 to > 2.5 for the 'hang' duration

In Dock64.exe the thread is called Dock64.exe+0x3a70 - it spikes from <0.01 to > 5.0 for the 'hang' duration

I run OD so that it autohides at the top of the screen (with the tabs showing) and to flyout if the mouse touches a tab (and autoselect that tab).

FWIW...

Cheers,

Chris.

Reply #27 Top

I was thinking what would make it want to delay on closing a program. Then I remembered I enabled "Show indicator under running programs". So I thought I'd put the Dock64 files back in place and try turning that off. However after putting the Dock64 files back in play, I'm no longer getting the delays. I still have the Indicator running and did nothing more than add the files back. Put the weather docklet back and it is working. I've done a couple of reboots to be sure. OD is still the last program to load, but I'm not seeing any delays. I wonder if an MS update might have fixed it. I also recently updated Intel Rapid Storage (not sure that would matter)...

Reply #29 Top

Not sure if this will help anyone else - but... I was running version 2.10.x and I have it set to automatically update. I even manually tried updating a number of times and it always said I had the latest version. I then went to my download portal and looked. There was a version 2.20.x ??  So I backed up OD and uninstalled it. I reinstalled version 2.20.x - all my settings stayed and the delay (at least at this point) is gone!

Reply #31 Top

Stardock, can someone respond to this issue?  Do you acknowledge it is an issue?  Is it not and thus it is something on my machine (and everyone in this thread)? Any workarounds other than disabling the 64 bit items?  And why does doing that fix the problem?

Reply #32 Top

Quoting Jafo, reply 18


Quoting martin166,

I'm running Win Pro 10 x64 with 8G of memory, RAID array and an Intel I5 processor. After login, everything comes active but there is a delay before I see the Dock at the bottom. I also have a few flyout menus on the Dock - not sure if that adds anything to the mix.  Randy, do you shutdown your computer or put it to sleep or hibernate? I'd be interested from a cold boot and login, how long after login before you see the Dock?



Since Win8 and beyond, Microsoft changed their boot sequence to give the impression of a fast-loaded desktop, however all third-party applications were left to the end of the sequence which gives the impression [only] that there is a delay for such things as Object Dock loading.

The reality is that the overall boot time is not much different from Win7 and earlier - it only looks that way.

Only real gauge of load times is watching drive activity.  When that stops the sequence is complete...;)

 

Just set OD to not load at startup, reboot, wait until hdd led turns calm, launch OD: it seems that the OS is loading photoshop.

OD is damn slow to load, and stardock does not want to improve it.

With modern hardware it should load in 2 secs

Reply #33 Top

There is an issue. As noted earlier in this thread, removing the 64 bit piece removes the delays and lets it load a bit faster. I'm just shocked Stardock is not addressing, commenting or otherwise acknowledging this issue. Everyone on this thread is in agreement so go figure...

Reply #34 Top

Hi There

I found that Windows Defender and Malware bytes scan object dock and had some improvement in performance by excluding the Stardock folder from both programs searches, effectively trusting Objectdock implicitly

Reply #35 Top

Quoting RandyMck2005, reply 1

not sure if this will help you but stopped dock64.exe and dock64.dll from running by renaming it to dock64.exe.old and dock64.dll.old and it stopped being slow and hanging in windows 10. Im not sure what impact that will have on the program but it seems to be working just fine.

 

Resurrecting this long dead topic just to say a big Thank You to RandyMck2005 is probably no excuse, but I believe that this needs to stay alive just a while longer..

Heaps of love all, and Thanks Randy :)

Brian :)

Reply #36 Top

Just worth noting:

 

Quoting martin166, reply 11

I heard back from support and I'll share it here. They said the Object Dock pages are up-to-date. That means it is only supported on Win8 and below (not Win10). I also asked the future of Object Dock and the response was "It is unknown"

Reply #38 Top

Yea, I was using it that way (which if I remember correctly breaks any of the real time applets like weather). I really like the program and want them to continue to support it. But if they are not going to certify it under Win10 and not provide updates, then I'm done. It will just be a matter of time until it causes more issues, and at this point unless something changes - it looks like a dead-end product.

Reply #39 Top

Ya, this is still a problem in 2018. I have to run 32bit Object Dock in windows 10, because the 64bit version lags out and is just terrible. Glad I found this post though. Its running fine now in 32bit mode.

+1 Loading…
Reply #40 Top

Thanks RandyMck2005 this solves my problem with "Hanging delays (Win 7, 10)"

The renaming of dock64.exe and dock64.dll "solves" the problem.

But stardock hast to fix this incompatibility to windows10 x64 ASAP we pay for this software . 

KR Nobentrix

Reply #41 Top

I can't believe that this issue goes all the way back to 2015 and hasn't been resolved. This only became an issue for me around a month or so ago. As a very long time ObjectDock user I didn't have an issue for many many years. Also autoupdate doesn't work.

Reply #42 Top

Cariied out the same change and all is OK on Windows 10 64 bit. Up to date version

Reply #43 Top

Stopping dock64.exe and dock64.dll worked for me i thought all was lost till i found this post.

Thanks RandyMck2005.

Reply #44 Top

Sorry Guys for the previous post, I meant to write I added .old to these two files like suggested dock64.exe.old and dock64.dll.old and Its worked for me I thought all was lost till I found this post.

Thanks RandyMck2005.:)  

Reply #46 Top

Good morning. In W10 pro I7 + 16gb Ram + 3Gb video , ObjectDock is lag. It is very slow to pass the cursor. Optimize please, developers.

I have the licensed version.

Thanks.

Reply #47 Top

Quoting XabiGus, reply 46

Good morning. In W10 pro I7 + 16gb Ram + 3Gb video , ObjectDock is lag. It is very slow to pass the cursor. Optimize please, developers.

I have the licensed version.

Thanks.

Hello,
Sorry to hear you are having issues. But, ObjectDock is not supported in Windows 10 environment.

Basj,
Stardock Community Assistant.

Reply #48 Top

Just wondering if the program that got me "sold" onto Object Desktop is going to be updated. I tried the Winstep Nexus Dock, and it is nice, but isn't quite the same. I do miss Desktop X too, but it seems that at least the Dock could be updated to still be useful in Windows 10.

Reply #49 Top

Quoting XabiGus, reply 46

Good morning. In W10 pro I7 + 16gb Ram + 3Gb video , ObjectDock is lag. It is very slow to pass the cursor. Optimize please, developers.

I have the licensed version.

Thanks.
Quoting basj, reply 47


Quoting XabiGus,

Good morning. In W10 pro I7 + 16gb Ram + 3Gb video , ObjectDock is lag. It is very slow to pass the cursor. Optimize please, developers.

I have the licensed version.

Thanks.



Hello,
Sorry to hear you are having issues. But, ObjectDock is not supported in Windows 10 environment.

Basj,
Stardock Community Assistant.


Unbelivable that this has not been solved yet properly for Windows 10, its October 2019 and my ObjectDock is lagging so much, especially when I close my browser. Takes 5-10 seconds at least before I can open another program on the dock.

However, like the second post suggestion, renaming the Dock64.exe and Dock64.dll solved the lagging. StarDock, you have gotten paid for this program from thousands of users, contact your programmer and get this program working properly without the renaming hack. 

 

Reply #50 Top

Quoting basj, reply 47

Hello,
Sorry to hear you are having issues. But, ObjectDock is not supported in Windows 10 environment.

Basj,
Stardock Community Assistant.

I wonder how many people is going to ignore this statement without being misled by some of members claiming it's fine to run it on Win 10. :rolleyes: