Goth667

Join Date 07/2006

Objectdock 3 starts apps as child processes

If an app crashes that you started from Objectdock...

Hi,

I like Objectdock and am happy to see it come back.

Sadly it does have a strange behavior that I would like to turn off. When you start an application through Objectdock it starts as a child process of Objectdock, this means that if the application crashes or you need to use Taskmanager on it, you can't. As a child process you can only end the parent to stop all the child processes, meaning it would not only need you to end Objectdock but also every other application you started with it.

Is it possible to turn that behavior off and let it start the applications as a new task?

Thanks

Michael

objectdock apps crahsing child process other stardock software

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Successfully updated karma reason!

Thank you for the assistance, I'm subscribed to the Thread so I wont miss an Answer.

Successfully updated karma reason!

Quoting ,

quoting post

Hi,

I like Objectdock and am happy to see it come back.

Sadly it does have a strange behavior that I would like to turn off. When you start an application through Objectdock it starts as a child process of Objectdock, this means that if the application crashes or you need to use Taskmanager on it, you can't. As a child process you can only end the parent to stop all the child processes, meaning it would not only need you to end Objectdock but also every other application you started with it.

Is it possible to turn that behavior off and let it start the applications as a new task?

Thanks

Michael

Hi Michael,

I haven't been able to reproduce your issue. I tried launching a few different programs from ObjectDock 3 (Notepad, ShareX, Calendar). Each program has showed up as its own parent process in Task Manager, and not as a child under ObjectDock 3.

Can you please elaborate with some more details? Does this occur only with TeamSpeak; is there anything else unique about what you might be doing to cause it?

Thanks,

Adam

Successfully updated karma reason!

Hi Adam,

thank you for your answer.

The issue was not only with Teamspeak but other applications as well. I only moved the link from the Desktop onto the bar, so there is nothing special to it.

I just tried it again and it didn't make child processes this time. I will keep my eye on it and if possible prvide a screenshot with other applications.

Thank you for the help.

Michael

Successfully updated karma reason!

Hi,

so I played a bit around and didn't get it to work except with TS3.

Once I start TS3 with Objectdock and then open the Task Manager everything is fine, but as soon as you close the Taskmanager and open it again, it will jump under Objectdock as a child process.

Thanks

Michael

Successfully updated karma reason!

Hi,

here is a new one.

The "Sound" App is a Windows App, you use it to switch to different devices.

Thanks

Michael

Successfully updated karma reason!

Quoting Goth667,

reply 6

Hi,

here is a new one.

The "Sound" App is a Windows App, you use it to switch to different devices.

Thanks

Michael

I tested this following your direction with the Sound Control Panel and was able to reproduce your findings.

I created a shortcut on the desktop and then drug to the ObjectDock. Opening it from the dock is shown below, and it opens as "Sound." If I open it from the Control Panel, it opens in its own process, and if I open it from the shortcut on the desktop, it opens in its own process. These open as Windows Host Process (Rundll32).

Successfully updated karma reason!

Would recommend trying in a Windows Sandbox environment to confirm if something unrelated to ObjectDock is affecting how your Task Manager behaves.

Following your steps in my testing with Windows 10 Sandbox environment:
I can see the Sound application running as a child process under Windows host process (Rundll32), but not as a child under ObjectDock. It behaves this way whether Sound is launched from desktop or on from ObjectDock.

With Windows 11 Sandbox environment:
With TeamSpeak, the issue still isn't reproducing for me.

Adam McGuinness
Customer Support Specialist

Successfully updated karma reason!

Teamspeak 3 has in the shortcut properties under Compatibility the checkbox "Run this programm as an administrator" was already ticked, when I moved it onto the Objectdeck App. Could that be the Issue?

Successfully updated karma reason!

This still seems to be an issue for me. I'm not sure if apps are actually opening as a child process of ObjectDock, or if Task Manager is interpreting something in a non-standard way from ObjectDock. An example from this morning is that I opened Outlook from the ObjectDock and Task Manager showed it running in its own process. I opened Task Manager a few minutes later, and Outlook was shown as a child process of ObjeckDock.

Windows 11 Pro - 22635.3566; ObjectDock 3 - 3.0.1.4

Successfully updated karma reason!

And now this is really weird.

Successfully updated karma reason!

And now an hour and 20 minutes later.

Successfully updated karma reason!

Hello,
I have forwarded this issue again to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Successfully updated karma reason!

FYI

I opened Outlook from ObjectDock this morning and have left it open all morning. Periodically checking the Task Manager, Outlook is shown as a child process of ObkjectDock and then later in its own process, and then again later as a child process of ObjectDock. There was also the time, shown above, where Artificial Inteligence (AI) Host was also shown as a child process of ObjectDock.

Something weird is going on here.

Successfully updated karma reason!