IcedTea6-plugin PluginAppletSecurityContext NullPointers

Oliver May oliver.may at dfc.be
Fri Feb 13 01:35:09 PST 2009


Seems my message got hold back by the mailing list because the large 
attachment, I uploaded the file to the website too:
http://geomajas.org/users/oliverm/freerunner-gpsApplet/applet-test.tgz

Hi Deepak!

  >>
  >> What website do you see this error on?
  >>
  >> As for PluginDebug.debug() ... its messages go to STDERR. However,
  >> debug() prints only if you have set ICEDTEAPLUGIN_DEBUG=true, and in
  >> that case, all OUT/ERR is redirected to /tmp/java.stdout and
  >> /tmp/java.stderr
  >>
  >> Cheers,
  >> Deepak
  >>
  >
  > Whoops.. should have checked the ML first.
  >
  > Okay, can you start the browser with the env variable
  > ICEDTEAPLUGIN_DEBUG=true , and then send the resulting log
  > and /tmp/java.std* files?
  >
  > Deepak
  >

I did some more testing, and put the applet I am using online with some
simple javascript <> java interaction, including the source files.

http://geomajas.org/users/oliverm/freerunner-gpsApplet/test-applet.html

The applet expects a gpsd running on localhost, but it wont crash
without it. You may forward local port 2947 to gpsd.mainframe.cx:2947
for some real data (real, but static, mainframe.cx is not moving :)).

Using this site I just did a test with debugging output:

debian-gta02:/tmp# ICEDTEAPLUGIN_DEBUG=true
debian-gta02:/tmp# export ICEDTEAPLUGIN_DEBUG
debian-gta02:/tmp# (iceweasel > /tmp/iceweasel.out) >& /tmp/iceweasel.err

so i have also gathered the iceweasel process out and err streams.

What I did is:
+Started iceweasel and opened http://geomajas.org....
+Waited until the applet was completely loaded (cpu idle)
+Clicked on "Start gps" and waited like 10 minutes until cpu idle
+Clicked on "Get gps data", this returned null in the textbox after half
a second.
+Clicked on "Stop gps"
+Clicked on "Get gps data" again, wich actet the same way as before
+Closed iceweasel

Btw, there seem to be some real performance issues too, the first call
from javascript to java takes ages, esp. with debugging turned on. But
that could even well be the rather slow cpu (200 bogoMIPS, 400MHz arm).

Greetings!

-- 
Oliver May

DFC Software Engineering
GeoMajas partner www.geomajas.org

Brugsesteenweg 587
B-9030 Gent
Belgium
T: +32 9 236 61 96
F: +32 9 236 54 12
E: oliver.may at dfc.be
W: www.dfc.be




More information about the distro-pkg-dev mailing list