Scary memory error in Win8.

4 hours ago,AndyC wrote

*snip*

But I have to heavily disagree with the idea of adding explicit Close functionality to Metro apps

So what you are saying is, the app that can be run on the background and playing a loud music should never be closed explicitly by user?

This is not Mango where apps has limited multi-tasking ability. The Metro apps has all the background capability as any desktop app, which will keep playing annoying loud music until you terminate them in task manager.

(Anyway, this is rather off-topic. Because I am talking about memory error in regards to Metro apps' reliability. Meaning I am more concerned Metro apps can be unsafe without using the "unsafe" keyword. .Net apps are a lot safer unless you are specifically mark "unsafe").

6 hours ago,cbae wrote

 The memory demand shot up to about 3.5GB.

Don't ever run Weather, it takes about 150MB and it will run without ever going into suspension.

4 hours ago,magicalclick wrote

*snip*

This is not Mango where apps has limited multi-tasking ability. The Metro apps has all the background capability as any desktop app, which will keep playing annoying loud music until you terminate them in task manager.

They don't have all the background capability of desktop apps. They are suspended when put in the background and can't do anything. Background audio and downloading via BITS are pretty much all they can do and the behaviour of audio is dependent upon whether it's a game, communications or music app. It's certainly not ideal in the current build, but don't confuse buggy behaviour with the ultimate intention of the OS.

(Anyway, this is rather off-topic. Because I am talking about memory error in regards to Metro apps' reliability. Meaning I am more concerned Metro apps can be unsafe without using the "unsafe" keyword. .Net apps are a lot safer unless you are specifically mark "unsafe").

But there is no evidence they can be "unsafe", you can't even remember what the error message you actually saw was. Maybe you hit an OS bug or maybe a driver had issues. At this point it's all a bit anecdotal because nobody really knows what it is you're talking about. 

4 hours ago,magicalclick wrote

*snip*

Don't ever run Weather, it takes about 150MB and it will run without ever going into suspension.

It will be suspended after a while, though it does seem to take an unusually long time. I think the background suspension code might still be a bit work-in-progress as there were a few demos at Build where things didn't quite suspend in the way they should. i do have to wonder why Weather and Stocks seem to consume so much memory and CPU for what seem to be fairly simple apps. Bad intern coding or deliberately written to stress test the system?

1 hour ago,AndyC wrote

It will be suspended after a while, though it does seem to take an unusually long time.

either way, it still takes 150MB regardless which state it is in, which was the main problem what cbae had, running out of memory.

As for "Limited multi-tasking"? (edit) nvm, this is really not my topic.

(Anyway, this is rather off-topic. Because I am talking about memory error in regards to Metro apps' reliability. Meaning I am more concerned Metro apps can be unsafe without using the "unsafe" keyword. .Net apps are a lot safer unless you are specifically mark "unsafe").

Well that's because Metro itself isn't built in .NET, it's built in C++.

Also Windows 8 is independently pen-tested by lots of private sector and public sector organisations both before release and after release (that's where a lot of the critical security patches come from), and crashes on customer computers are reported via WinErr to Microsoft for fixing too, so I wouldn't be too worried that these crashes on the Win8 beta are going to lead to your computer being compromised.

And anyway, where did this "I didn't use unsafe therefore my program can't crash or experience memory corruption" mentality come from? It's easy to make .NET crash without using the unsafe keyword, or even worse, the "It's .NET therefore it's unexploitable" attitude (which in my experience is the opposite of the truth - you try making a dummy vulnerable C program and see if you can exploit it, and then try making a dummy vulnerable ASP+SQL program and see if you can exploit that, and tell me which is easier to do).

2 hours ago,magicalclick wrote

*snip*

either way, it still takes 150MB regardless which state it is in, which was the main problem what cbae had, running out of memory.

Windows 8 immeadiately kills suspended processes if it needs the memory, so that isn't an issue unless you're running in a VM and it is pretending there is more physical RAM than there really is available. I really recommend everyone watchthis session, because it explains a lot about the model behind Metro apps and why it doesn't need a close button.

I've had a memory error pop-up also, both times it said unable to read memory location with an address displayed.

55 minutes ago,smithduluth wrote

I've had a memory error pop-up also, both times it said unable to read memory location with an address displayed.

yeah, I think that's pretty much what mine said. Please share the details when you get the error again. Thank you.

@AndyC:

interesting, I wasn't able to push over 100% RAM myself. I didn't have enough Metro apps to test it out. I didn't use desktop app since that wouldn't the same. Anyway, personally I don't like this below, from both CPU and Memory usage of a simple Metro usage.

And Black Screen of Semi-Death.