[Bob Smith <bobsmith1@marketweighton.com>]

I have no idea.  without knowing what Editor.setPage() does, I have no
idea what your problem might be.  I don't *think* the URL constructor
should be the problem here.  what if you declare a local URL variable,
construct he URL object and assign it to this variable and then make
the setPage() call using this as the argument, so that you can measure
the time this takes to see if it is really the *constructor* that
takes time.  something like this:

  import java.net.URL;
  ....
  ....
  long t = System.currentTimeMillis();
  System.err.println("before");
  URL url = new URL( "...url..." );
  System.err.println("after, took " + (System.currentTimeMillis() - t));
  Editor.setPage(url);

...so you'll see if the URL constructor is the culprit.

as I suggested before, if the hashCode() method of URL gets called,
this will trigger address resolution of the host part of the URL,
which might, on a really badly configured¹ Linux box, take a while.

what does Editor.setPage() do?  will this add URL to a Set or use it
as a key in a Map? (or even a value in a map which you later extract
the Map.Entry set for?).

¹) check /etc/resolv.conf if you have multiple nameservers entries in
  the config and if the probing sequence contains DNS servers that
  are unresponsive/dead.

-Bjørn

..

..

..

..

...

..

Stuff these 'code snippets', I say!

It would be a lot simpler for others to ascertain exactly
what is happening when you provide a single exactly reproducible
problem (as was expanded in the SSCCE document to which
I linked in my first reply).

Note that ..
a) The code has changed from first to second post.
adding an URL to a map is (probably) going to cause
a very different set of code instructions to be performed
than if you set an editor to the URL.
b) In only 1 in 15 cases[1] does the code snippet supplied actually
reveal the line/lines in code that are the problem.
c) These code snippets still do not reveal the actual contents
of the URL, which you have thus far listed as (the very unhelpful)
"...url..."

I could go on asking 20-30 questions that might help narrow
down the possibilites to what is actually happening, but
since it is your problem and I have already described to
you the best way to *answer* those questions (as well as the
100-500 that might be asked based on unexpected replies to the
20-30), I won't.

I feel this problem would be best advanced to a solution by
*you* supplying the exact code that are using.

[1]  86.7% of statistics are made up on the spot.