Status: Resolved (View Workflow)
Suse Linux 11 Sp2, Oracle Java 1.7.0_45, jenkins with internal web interface, Mozilla FireFox 37.0.1 on Windows 7
I updated jenkins from version 1.596 to version 1.609.
No I get a script timeout if I try to configure some of the larger jobs.
I can configure small jobs without any problems.
I increase the firefox script timeout from 10 seconds to 100 seconds.
Now I can configure the jenkins jobs, but it takes a very long time to start editing.
With version 1.596 it was possible to start configuring of the same larger jobs in the predefined timout of 10 seconds
- is related to
JENKINS-32027 Jobs with very long configuration cause script errors in browser and extremely long loading times (10+ minutes)
I followed the instructions from Scott (Global Security -> In the Markup Formatter section, ensure: Safe HTML is selected and Click on Disable syntax highlighting) and now I can configure jobs in Firefox, but Chrome and Safari are still broken. At least we have a workaround.
it seems that the bug is fixed.
I have two jobs, which took about 10 minutes to open for edit with jenkins up to 2.11
Since I use 2.12 the same jobs takes about 10 to 20 seconds to open for edit.
And the browser does'n allocated about 10 GB of memory to open the job any more.
There is a problem with CodeMirror and textarea windows.
I just upgraded to LTS 1.642.3 this weekend and getting a little rubbing from my comrades about how long the configure load times are.
I have one 2x4 Matrix multi-step job with conditionals that have shell, python, and windows batch executes. The configure page for this job generates 8-10 timeouts in codemirror.js and takes minutes to load.
Common timeouts are on lines 1247, 1207, 853
These deal with the gutter and scrollbar as far as I can tell.
I've spent Saturday trying everything I can to somehow just DISABLE codemirror. But since it's core, not a plugin, and there's no exposed configuration for it, I'm pretty much stuck with it's behavior. Is it possible to turn it off?
The setting in security for syntax highlighting is not related, the number of builds or history is not related. This is purely codemirror barfing on complex jobs with recursive textareas.
I'm surprised codemirror is not a tag/label on this ticket.
I am creating a sanitized config.xml which I hope to upload to this ticket in the hope that it helps with a resolution.