Cascades Development

[yogeshwarp]

onPopTransitionEnded: page.destroy() does fix the issue. its grayed out for few seconds but at least it exists on its own.

killing the process from the terminal also helped so looks like some cleanup activity is not happening. how much its due to WebView not sure but that seems to be the common element so far

[ekke]

---

peter9477 wrote:
...so I ran "pidin" and it was still listed. ... I used "slay" with the PID to terminate the app, and immediately the icon returned from the ghosted state and I could run it again.

---

thx Peter - this works for me, too. helps while development but not the users ;-)

btw: is there a doc about such useful commands like pidin and slay ?

[peter9477]

---

ekke wrote:

thx Peter - this works for me, too. helps while development but not the users ;-)

btw: is there a doc about such useful commands like pidin and slay ?

---

This should cover everything useful: http://developer.blackberry.com/native/beta/reference/com.qnx.doc.neutrino.utilities/topic/about.htm...

[ekke]

---

peter9477 wrote:

---

ekke wrote:

thx Peter - this works for me, too. helps while development but not the users ;-)

btw: is there a doc about such useful commands like pidin and slay ?

---

This should cover everything useful: http://developer.blackberry.com/native/beta/reference/com.qnx.doc.neutrino.utilities/topic/about.htm...

---

THX

[lew]

more info:

in my case, it appears to be caused only with a build from a BETA4 QDE...When i build same code/app on BETA3 QDE, this closing state never happens...no issue at all.

i couldn't test with a device-release profile as my app no longer builds correctly for this profile on BETA4 QDE

can any of you confirm that this issue is not happening when you build your app with DEVICE-RELEASE profile?

(i'm thinking it is related to the debugger or some test/debug stuff that is being attached from the QDE to the device)

[peter9477]

I'm still using a device-release binary that was built with beta 3, so it's definitely not limited to just beta 4 stuff.

It's intermittent for certain types of cause, so that may be throwing off the analysis. If I force my app to crash in certain places, such that the shutdown code definitely never executes, then I can make this happen (I think) 100% of the time. If I exit "cleanly" it will still happen but only intermittently.

I also don't use QDE or Momentics so it's not inherently related to those either.

As I mentioned above, I no longer see the old "did not respond to exit" popup *ever*, and that makes me nearly certain this is directly related to whatever caused that, but the symptoms have simply changed. Most of us just took to ignoring that old popup, so we may not have noticed just how often it was occurring, compared to this "in yer face!" version of things...

[peter9477]

Oh, by the way, I think I can whip up a quick app that will make killing stuck apps this way easy, and if that works I'll upload it for everyone on the weekend.

[lew]

thanks Peter!

Looks like we'll need to do some more drilling down to find the source of this issue  

[bbquincar]

so in regards to finishing or starting a app with webview or ads in using the sim its a no go for now then.

i have to shut down my sim each time to get the new build to load. not cool

[peter9477]

Oh, does this happen on the sim too?  I don't use it, so I hadn't considered this.  I've got an app ready, but it's built for the device only. If this failure affects the sim as well, I'll have to do an x86 build as well I suppose. :-(