>
>Here's a bug report that I got from Ron House. I was able to duplicate >the problems with >an out of the box ij.ImageJApplet class. My whole browser crashed. To >duplicate one of >them, bring up the imagej applet in the appletviewer, select reload from >the appletviewer, >select help -> About ImageJ, then close the About window. This is with >ImageJ 1.35o. >It's important for us to be able to reload when necessary. I was able to >crash my browser reloading the applet on the ImageJ web site. I was >unable to run >the Plot Profile test against the ImageJ web site, because I don't know >how to load an >image from the ImageJ Web site, but I'm sure someone can try that. > >Here are the exceptions. I will be working on a fix sometime tomorrow, >but maybe someone >will get to this before me. > >Ron, > >Are you reloading the applet page, or just starting up a new applet >page? What happens >when you bring up two applets at the same time? I was reloading in my >test, and it really >throws a wrench into things. If we have to, we can deploy the >functionality as an application, >which may avoid these (and possibly many other problems), but probably >achieving many >more unknown problems (getting updates to the desktop, especially Macs--we >will have >to instruct the users to always go through the web page to start the >application I think). > From what I saw, there seems to be a pretty systemic problem with > reloads. We may >be hunting down these sorts of problems with applets for a long time. > >John > >Closing the about window: > >java.lang.ArrayIndexOutOfBoundsException: 7 >= 7 > at java.util.Vector.elementAt(Vector.java:432) > at java.awt.Menu.getItemImpl(Menu.java:230) > at java.awt.Menu.getItem(Menu.java:222) > at java.awt.Menu.remove(Menu.java:385) > at ij.Menus.removeWindowMenuItem(Menus.java:979) > at ij.WindowManager.removeImageWindow(WindowManager.java:272) > at ij.WindowManager.removeWindow(WindowManager.java:244) > at ij.gui.ImageWindow.close(ImageWindow.java:258) > at ij.ImagePlus.close(ImagePlus.java:296) > at ij.Executer.closeImage(Executer.java:203) > at ij.Executer.close(Executer.java:195) > at ij.Executer.runCommand(Executer.java:117) > at ij.Executer.run(Executer.java:63) > at java.lang.Thread.run(Thread.java:595) > > >Here's a second exception, by doing what Ron outlines below Plot Profile, >don't forget >to reload the applet. > > >java.lang.NullPointerException > at ij.util.Java2.setAntialiasedText(Java2.java:28) > at >ij.process.ImageProcessor.getStringWidth(ImageProcessor.java:936) > at ij.gui.Plot.draw(Plot.java:360) > at ij.gui.Plot.show(Plot.java:447) > at ij.gui.ProfilePlot.createWindow(ProfilePlot.java:116) > at ij.plugin.filter.Profiler.run(Profiler.java:23) > at ij.IJ.runFilterPlugIn(IJ.java:197) > at ij.IJ.runPlugIn(IJ.java:126) > at ij.Executer.runPlugIn(Executer.java:171) > at ij.Executer.runCommand(Executer.java:133) > at ij.Executer.run(Executer.java:63) > at java.lang.Thread.run(Thread.java:595) > > > > > >>John, >> >>An old problem that we've experience with imagej before seems to have >>returned. I thought it was fixed with the latest imagej beta, but >>apparently not. So, now I'm not sure why it appeared to be working for >>me at one time. The scenario is >> >>1) start imagej applet >>2) draw a box or line >>3) select "Analyze" and "Plot Profile" >>4) close image j >>5) repeat 1 thru 3 >>6) null pointer exception occurs >> >>in fact even doing a "about imagej" on the second (or any susequent run) >>causes a null pointer exeception. I hope we can fix this, it makes it >>very hard to demo, if we have to restart the browser after loading each image. >> >>Ron |
Free forum by Nabble | Edit this page |