normal.
After check the logs, all code has SIGSEGVed inside libwebcore.so, it
always hard to address the issue code as it is happened inside native
C code.
But on the other hand, I notice this kind of browser crash always
happened in phone low memory status, and Browser also always print log
as E/memlog etc.
So, my question is:
Is phone low memory could lead to Browser SIGSEGV in libwebcore.so?
Thanks!
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment