Hi guys & girls 
First, I have no idea about internals of the SDK.
Second, my questions might have been already asked, please excuse me and redirect me.
I've tried portable skype & pidgin. Hope I'm not the only who checked the processes in Task Manager (TM). And it's very strange that each X application has two own process: XPortable.exe (1) & X.exe (2). Obviously (1) launches (2). And it's the fact that (1) could be easily killed in TM: (2) continues running as usual.
So the question: why not to quit (1) process after (2) has been launched?
Reasons are quite obvious - to save RAM and ensure no spyware running (joke)
Thanks
R
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Yes, the launcher does start the main program. However, that is not the only function it has. Depending on how intrusive (un-portable) the program is, the launcher waits for program termination and will clean up after it... undoing the registry entries it might make and moving configuration files it insists on writing to the local machine back onto the USB drive.
So if you kill the launcher process the portability goes out the window.
neutron1132 (at) usa (dot) com
some Launchers quit after launching the actual App because they arent needed any more but if they keep running there is usually a reason for that.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
Just an idea, if we have the same approach for all portable apps, and it's "copy-pasted" into all apps, could it be implemented only one win service, which will be responsible for watching and cleaning up all running portable apps?
If possible then it will make sense since more and people like portability and have more than one portable app on their devices. Having installed only one win service it may resolve the problem with 2N processes instead of N.
Thoughts?
You mean 1 XXPortable.exe process for, lets say, 10 running portable applications, instead of current 10 XXPortable.exe instances for 10 running apps?.. Brilliant! Then, all it takes is 1 process to crash... Why hasn't someone thought of that sooner?
Btw, I'm "being Darkbee" here...
I hope you realize that it's not such a good idea, at least IMO, to do what you ask. Mozilla is even trying to make firefox.exe have a separate process for each tab, in case of a crash...
My posts are old and likely no longer relevant.
They already have a separate process (in beta) now for a plugin container.
Oy! Stop taking my name in vain!
And how am I suppose to make sarcastic yet insightful comments on this thread now?
@ romb: [...] and "Welcome to PortableApps"!
@ Darkbee: (everything else)
Sorry, I thought you wouldn't mind
Also, the line was supposed to be like this:
I don't know where the
Glad you're here now. I haven't seen your ("Darkbee-ish") posts recently, which automatically reduced the fun factor of being here by about 75%... Ok, 50%... Ok, ok - about 10%! Happy? 
:Ppart went...Well.... Comment on my signature, if all else fails. You're bound to get a sarcastic point on my hate towards Google "the spy agency" (hence I'm suggesting startpage [dot] com)... Anything? ...yet?... How about now?
Take care, and don't take anything I wrote personally... or too seriously...
My posts are old and likely no longer relevant.
I don't and I didn't. I was being sarcastic.
I was on vacation for just over a week, hence no posts. Don't worry, normal services will resume.
I'd say just what was said above - they're not portable unless they do things at the end, cleaning up, moving files back, registry things, etc. In short, one process is not enough.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
As said it's just a proposal.
How often did you see crashed win services? I didn't remember. Think it depends on their design.
Here initialization/cleanup staff required, so XPortable.exe may be invoked from the service on app exit (e.g. subscriber pattern). If there is an error inside XPortable.exe, it shouldn't result in crashing the service. So XPortable.exe is required, but it runs only twice per X.exe lifecycle: on launch & on exit (and isn't running all the time).
One extra process is a price to pay for portability. Not all users may know that.
That's just not a practical or reasonable way of doing it. For starters, services require administrative privileges. Secondly, in case of power failure or similar a broken service tends to cause a little bit more trouble than a little bit of data. Also it would be very troublesome to keep track of all the different processes from portable apps, and it would actually be far less efficient than the current system, because you'd have to keep checking that a whole hoard of processes are still there rather than just latching on to one and waiting doing absolutely nothing until it's finished.
You say that one extra process is a price to pay for portability; I wouldn't call it a price at all. If you can't cope with an extra few megabytes of memory being used (and in the new PortableApps.com Launcher memory usage while waiting is down to a couple of hundred kilobytes, that will start coming for all our apps) then you probably don't have enough memory. An extra process is really nothing to worry about. Users don't need to know about it.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1