I am the developer who wrote the article, and just wanted to update people that it is now in the store. While I am happy to finally see it released, I was a little annoyed that it just passed, as I didn't make any changes since the 6th failure. I was just told to re-submit so they could escalate internally (before the article went up, so it wasn't due to that), and I just assumed they would have someone looking closer at the failure to explain what it was. It's frustrating that after all of this, I still don't know what was causing the crashing. If the issue was on their end though, hopefully it will just be one of the many kinks they have to work out, and it won't affect anyone on-going.
Here is the link to the app.
http://apps.microsoft.com/webpdp/app/memorylage/269b17da-9475-4339-9786-2131c9880d52
I am the developer who wrote the article, and just wanted to update people that it is now in the store. While I am happy to finally see it released, I was a little annoyed that it just passed, as I didn't make any changes since the 6th failure. I was just told to re-submit so they could escalate internally (before the article went up, so it wasn't due to that), and I just assumed they would have someone looking closer at the failure to explain what it was. It's frustrating that after all of this, I still don't know what was causing the crashing. If the issue was on their end though, hopefully it will just be one of the many kinks they have to work out, and it won't affect anyone on-going. Here is the link to the app. http://apps.microsoft.com/webpdp/app/memorylage/269b17da-9475-4339-9786-2131c9880d52