We're having some random crashes using the ArchitectView (Wikitude SDK 1.1.1) on the Milestone and Nexus S devices. Unfortunately no direct steps to reproduce but here is the log output:
10-16 12:29:55.303: I/dalvikvm(2769): at android.webkit.BrowserFrame.stringByEvaluatingJavaScriptFromString(Native Method)
10-16 12:29:55.342: I/dalvikvm(2769): at android.webkit.BrowserFrame.loadUrl(BrowserFrame.java:245)
10-16 12:29:55.342: I/dalvikvm(2769): at android.webkit.WebViewCore.loadUrl(WebViewCore.java:1563)
10-16 12:29:55.342: I/dalvikvm(2769): at android.webkit.WebViewCore.access$1400(WebViewCore.java:52)
10-16 12:29:55.342: I/dalvikvm(2769): at android.webkit.WebViewCore$EventHub$1.handleMessage(WebViewCore.java:949)
10-16 12:29:55.342: I/dalvikvm(2769): at android.os.Handler.dispatchMessage(Handler.java:99)
10-16 12:29:55.381: I/dalvikvm(2769): at android.os.Looper.loop(Looper.java:143)
10-16 12:29:55.381: I/dalvikvm(2769): at android.webkit.WebViewCore$WebCoreThread.run(WebViewCore.java:622)
10-16 12:29:55.381: I/dalvikvm(2769): at java.lang.Thread.run(Thread.java:1096)
Any thoughts on how we can prevent that from happening?
M
Markus Eder
said
about 11 years ago
Hello!
Especially on older devices like the milestone, the number of Architect objects in a world that can be shown is restricted and can vary depending on the current memory usage. What you can do on those devices is restrict the number of currently shown objects. Also it helps if you delete ARchitect objects as soon as you don't need them anymore in your ARchitect world.
Hope that helps
Markus
Y
Yegor Vedernikov
said
about 11 years ago
Hi Markus,
We're already limiting the objects number and destroy the old objects on refresh, so it looks like there's not much we can do here.
Yegor Vedernikov