Thank you very much... This problem has been resolved with clearing the cache
webview.clearCache(true); webview.destroyDrawingCache(); However a Fatal signal 7 (SIGBUS) at 0x00000000 (code=128), thread 13497 (WebViewCoreThre) occurs so let's get to that one ... Op woensdag 26 oktober 2016 09:18:27 UTC+2 schreef sardar khan: > > You can see these links > http://stackoverflow.com/questions/4973310/signal-11-sigsegv-crash-android > > http://stackoverflow.com/questions/18755318/webview-destroy-causing-fatal-signal-11-crash > > http://stackoverflow.com/questions/22566215/fatal-signal-11-sigsevg-in-my-webview > hope this will help .Thanks > > On Wed, Oct 26, 2016 at 11:58 AM, <[email protected] <javascript:>> > wrote: > >> Hello, >> >> I wrote an (really basic) application to control access for a building. >> This application exists of multiple buttons (10 in total). >> Per door there are 2 buttons. One button acts as an pulse buton. When >> clicking the pulse button a timer function will be enabled and after 5 >> seconds the function will be disabled. >> The other button enables or disables the function manualy (without a >> timer). >> >> When the function is enabled a URL request is send out to load within a >> WebView. The URL that is requested is an URL trigger for a webrelay which >> will trgger the door to unlock. >> When the function is disabled a URL request is send out to load within a >> WebView. The URL that is requested is an URL trigger for a webrelay which >> will trgger the door to lock. >> For testing the URL request i used URL's like: >> http://www.cisco.com >> http://www, nu.nl >> >> The URL's requested will appear in a Webview (which will be invisible in >> the final version). >> Each door has it's own door WebView. >> >> So for short: >> One door has: >> 2 buttons; >> 1 timer function; >> 1 WebView. >> >> There are 5 doors in total. >> >> Now the problem coms that after running this error will occure: >> A/libc: Fatal signal 11 (SIGSEGV) at 0x0000001c (code=1), thread 25881 >> (WebViewCoreThre) >> >> After searching on the internet, i learned this could be a memory issue. >> But i don't have a clue to how address this, or what the problem could >> be. I tried to eleminate the images that i used, but that didn't work. >> >> The application is develloped for Android 4.1 (Jellybean). >> >> How can i resolve this problem ?? >> >> Regards. >> >> Dennie >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Android Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/android-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/android-developers/c9b1e7b5-f16f-470a-a524-766993d9a777%40googlegroups.com >> >> <https://groups.google.com/d/msgid/android-developers/c9b1e7b5-f16f-470a-a524-766993d9a777%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/378dc448-d46a-4a6d-87d4-b28ff9863632%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
