If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
app suspended?
I saw this on a mailing list...
"I happened to be looking at Process Explorer just after I had closed the Flipboard App with the upper right corner X, and I saw that its state was 'suspended'. "I killed it, and started it up again. This time I used alt-F4. When I checked Process Explorer, there was no sign of Flipboard. "So, what does this signify???" |
Ads |
#2
|
|||
|
|||
app suspended?
Alek wrote:
I saw this on a mailing list... "I happened to be looking at Process Explorer just after I had closed the Flipboard App with the upper right corner X, and I saw that its state was 'suspended'. "I killed it, and started it up again. This time I used alt-F4. When I checked Process Explorer, there was no sign of Flipboard. "So, what does this signify???" That the app has an option to minimize its process to a tray icon or hide its window when "closing" its window (using the titlebar X icon) and that option is enabled. The function of the X object for the window object can change. Use File - Exit instead. Alt+F4 requests the process to exit, not merely close or hide its window. A process can run without a window. |
#3
|
|||
|
|||
app suspended?
Alek wrote:
I saw this on a mailing list... "I happened to be looking at Process Explorer just after I had closed the Flipboard App with the upper right corner X, and I saw that its state was 'suspended'. "I killed it, and started it up again. This time I used alt-F4. When I checked Process Explorer, there was no sign of Flipboard. "So, what does this signify???" http://blogs.msdn.com/b/windowsappde...windows-8.aspx As we saw in the "managing app lifecycle" blog post, a Metro style app can transition between various runtime states. Based on this app lifecycle, we like to think of these key areas of verification: * Activated: verify the app through several activation paths * Running: verify the app at runtime * Suspended: verify the app suspends correctly * Resumed: verify the app resumes correctly * Terminated: verify the app terminates * Not running: verify behavior when your app is not running http://blogs.msdn.com/b/windowsappde...live-quot.aspx The app lifecycle model in Windows 8 means that users no longer need to manage which apps are running. It also makes it easy for developers to craft a great user experience that doesn’t affect the device's battery or performance when the app is in the background. Using the new lifecycle events, your app will always feel alive, even though it never runs when it is off-screen. [The rest of that article goes on to explain the concepts] ******* Now you know why the XBOX Music player in Win10 Preview, stops playing music when you iconify it. As soon as the application loses focus, the music stops. And you can see that to have the music playing, is a violation of the above model. For XBOX Music to work, they'll need a new state in the model, that allows a program to continue running, but without the GUI being visible on the screen. Also, the above article omits one other state. The Windows OS continues to have a "zombie" state for a process. And that state even existed in Unix, so the concept has been around for decades. A zombie is a task that needs to be harvested by Init (or whatever the boss task is in the system), but it hasn't happened yet. As a user, there's nothing you can do to make a zombie go away (short of rebooting). On Windows, such a zombie would exist as an oversight, rather than by design. Yet, the OS needs a notation for such a situation, which is why you might see such a status in Task Manager some day. Normally, a task entering the "terminating" state, disappears rapidly. But if there is a problem with the shutdown process for the thing, then it gets a zombie status, and as far as the user can tell, absolutely nothing on the computer cares about it any more. Paul |
#4
|
|||
|
|||
app suspended?
Maybe Windows 8.1 has been updated. I tried close button and Alt+F4 with a
few Apps and now Alt+F4 closes effectively the App. "Alek" escreveu na mensagem ... I saw this on a mailing list... "I happened to be looking at Process Explorer just after I had closed the Flipboard App with the upper right corner X, and I saw that its state was 'suspended'. "I killed it, and started it up again. This time I used alt-F4. When I checked Process Explorer, there was no sign of Flipboard. "So, what does this signify???" |
#5
|
|||
|
|||
app suspended?
Wolf K wrote on 7/2/2015 9:18 AM:
On 2015-07-01 8:37 PM, Alek wrote: I saw this on a mailing list... "I happened to be looking at Process Explorer just after I had closed the Flipboard App with the upper right corner X, and I saw that its state was 'suspended'. "I killed it, and started it up again. This time I used alt-F4. When I checked Process Explorer, there was no sign of Flipboard. "So, what does this signify???" That the app is still in memory, not running. The OS can restart it without having to reload it. Usually, it also means that related current data, or pointers to it, is preserved. Huh! I thought that the X was the same as for a desktop program. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|