Yup that fixed it. Any idea what the story is? That is the only link that was forcing the browser to crash - why would clearing the cache, etc fix the problem?
Yup that fixed it. Any idea what the story is? That is the only link that was forcing the browser to crash - why would clearing the cache, etc fix the problem?
Why that link? No idea.
Why clearing the cache, etc would help... is because there is a general suspicion that PB running out of memory is what causes at least some of these browser crashes. Clearing the cache releases some memory back to the pool.
Yup that fixed it. Any idea what the story is? That is the only link that was forcing the browser to crash - why would clearing the cache, etc fix the problem?
I think it may have more with something in the Local Storage thats affecting the website. Something possibly getting corrupted and causing the site to crash.
I turned off Flash and so far it has not crashed. Could still be a mem issue but have well over 300 megs showing as being free.
It is disappointing to know that 1.0 did not have this issue much and now 2.0 is plagued with it. The one item that RIM boasts about on the PB and it is worse then the day it came out.
Whatever the heck is causing RIM needs to jump all over it but then RIM has to see it is an issue. So far RIM has not really said it is an issue they are working on fixing.
They always seem surprised...not good.
I turned off Flash and so far it has not crashed. Could still be a mem issue but have well over 300 megs showing as being free.
It is disappointing to know that 1.0 did not have this issue much and now 2.0 is plagued with it. The one item that RIM boasts about on the PB and it is worse then the day it came out.
Whatever the heck is causing RIM needs to jump all over it but then RIM has to see it is an issue. So far RIM has not really said it is an issue they are working on fixing.
They always seem surprised...not good.
Tim
I think they have a full page of problematic links/sites in the beta zone and that they are precisely investigating each of them (can't remember who reported this, but I remember he's a trusted CB and beta zone user).
Actually, when debugging these erratic behavior, it's hard to tell whether it's browser / memory usage / site includes related ... I suspected once ads (which can change for each user, depending on his profile) to be the "trigger" ...
What has been reported (twitter,here) is that the browser is on the top list of enhancements number in next update.
Hopefully, side-effects (memory, cache) should be treated as well.
