[
https://issues.jenkins-ci.org/browse/JENKINS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163201#comment-163201
]
Kohsuke Kawaguchi commented on JENKINS-9142:
--------------------------------------------
The URL in question "$stapler/bound/GUID/" is used for lazy rendering of
fragments. These IDs are session local, transient during a life of an instance.
So it is unlikely that how $JENKINS_HOME came into being (whether it was an
upgrade or a fresh install) is related to the bug.
I noticed that those transient objects are held via {{WeakReference}}. I wonder
if people seeing those issues are under strong memory pressure, and those weak
references are getting released before they are actually used?
Could someone check my hypothesis by bumping up the heap size? I'll add some
logging so that we can verify this.
> "Add Build Step" button broken in job configure page
> ----------------------------------------------------
>
> Key: JENKINS-9142
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9142
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Environment: CentOS linux x86_64 firefox 3.6.15
> Reporter: Andrew Helfer
> Priority: Blocker
>
> after upggrading from Hudson 1.395 to Jenkins 1.403 and installing the
> msbuild and VCviewer plugins, the add build step button no longer works.
> Doesn't add a shell window to the web UI, no matter what I do.
> Last known successful action was to delete a step, first unsuccessful action
> was to add an msbuild step.
> there are no Java console errors or warnings, and nothing in the logs to
> suggest anything wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
