Thread: Browser unexpectedly closes
View Single Post
Old 09-03-2011, 09:40 AM   #39
Gunnerp245
Gadget Freak
Gunnerp245 ought to be getting tired of karma fortunes by now.Gunnerp245 ought to be getting tired of karma fortunes by now.Gunnerp245 ought to be getting tired of karma fortunes by now.Gunnerp245 ought to be getting tired of karma fortunes by now.Gunnerp245 ought to be getting tired of karma fortunes by now.Gunnerp245 ought to be getting tired of karma fortunes by now.Gunnerp245 ought to be getting tired of karma fortunes by now.Gunnerp245 ought to be getting tired of karma fortunes by now.Gunnerp245 ought to be getting tired of karma fortunes by now.Gunnerp245 ought to be getting tired of karma fortunes by now.Gunnerp245 ought to be getting tired of karma fortunes by now.
 
Gunnerp245's Avatar
 
Posts: 1,169
Karma: 1043832
Join Date: Nov 2007
Location: US
Device: EE, Note 8
Quote:
Originally Posted by ivanjt View Post
No easy way that I know of and since the javascript engine has nothing to do with java the programming language, knowing the version isn't going to help very much.

I think the problem is that the javascript engine tries to call APIs that we don't have on the EE and PE and when it gets no reply it exits in a way that crashes the browser.
Okay, can we determine which APIs it is trying to call? I have alogcat installed on my rooted-ermine EE; incidentally, I have a second EE not-rooted running Dingo 1.11.
Gunnerp245 is offline   Reply With Quote