Bug 527441 - java static variables are not well managed
Summary: java static variables are not well managed
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 10
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Deepak Bhole
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2009-10-06 12:37 UTC by gealach
Modified: 2009-12-18 09:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-12-18 09:44:13 UTC
Type: ---

Attachments (Terms of Use)

Description gealach 2009-10-06 12:37:01 UTC
Description of problem:

I have an applet with public static variables.
I deploy the applet in twice in the same page using frames:
  - in first frame, load applet and initialize static variable
  - second frame use the static variable

Applet is well loaded, but static variable ins'nt share between the two frames.
This worked well with Sun JVM

How reproducible:
systematic with Firefox 3.0.14. Didn't try with another browser

Actual results:
 value for static variables are not share

Expected results:
static variables should be shared between the two frames

Additional info:
 Worked fine with Sun JVM

Comment 1 Deepak Bhole 2009-10-09 20:22:11 UTC
Sorry, but this is not a bug -- it is by design (each instance is in its own classloader). The plugin specifications do not guarantee that a single JVM/loader will be running all applets. Additionally, allowing cross access creates potential security issues as hidden applets could try and steal information from static variables in running signed applets.

Comment 2 gealach 2009-10-23 10:11:35 UTC
  can you provide the url to that specification, and specify wich chapter.
  Additionnaly, i don't really understand the matter with security issues. Isn't it the responsability of the applet developer to make sure that sensible information are not easily catchable? for instance by not using static variables to store them?

Comment 3 Bug Zapper 2009-11-18 12:16:38 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 4 Bug Zapper 2009-12-18 09:44:13 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.