• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Tim Cooke
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Rob Spoor
  • Junilu Lacar
  • paul wheaton
Saloon Keepers:
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Scott Selikoff
  • Piet Souris
  • Jj Roberts
  • fred rosenberger

Self Signed Applet closes the browser

Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I created one self signed applet.
But when i run the applet some times it closes the applet (browser itself) and generated and error file. I am giving the details in the file
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x77f918be
Function name=memmove
Current Java thread:
at java.io.Win32FileSystem.canonicalize(Native Method)
at java.io.File.getCanonicalPath(Unknown Source)
at java.io.FilePermission$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.io.FilePermission.init(Unknown Source)
at java.io.FilePermission.<init>(Unknown Source)
at java.lang.SecurityManager.checkRead(Unknown Source)
at java.io.File.exists(Unknown Source)
at ilog.views.sdm.renderer.IlvStyleSheetRenderer.try(Unknown Source)
at sun.applet.AppletPanel.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
so kindly give me the solution so that the applet is not closed.And how can we see that the error file is not generated.
Saloon Keeper
Posts: 25614
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You have a lot more serious problem than you think. The browser isn't closing - it's abnormally terminating and it's doing so because of a memory access violation encountered while executing code in one of the Windows core DLLs.
This is probably due to a bug in the Win32FileSystem native class, since it shouldn't be attempting to move stuff around in memory it doesn't own. If you have access to a web-client machine running some other OS than Windows, you might try using that to see if there was something wrong with the access rules you set up.
    Bookmark Topic Watch Topic
  • New Topic