Is there any way to reply to a thread before I was subscribed? I'm pretty
much a noob when it comes to this mailing list process.
As for the deprecation, we use Nashorn heavily for our Edge transformation
layers and would need to find something that's at least backwards
compatible with our use
This seems like it could be a side effect of a bug I reported where using a
number as the key in an object in Nashorn made an array of the at least the
size of the number and then inserted in the index of the number specified.
The bug was fixed around that version that you mention.
On Mon, Apr
<
hannes.wallnoe...@oracle.com> wrote:
> The fix is in JDK 9 now. I will propose this to be backported this to 8u,
> which means it should appear in some 8u release soon, but I can’t make any
> promise about a specific release or date.
>
> Hannes
>
>
> > Am 09.01.2017
very inefficiently in Nashorn. I’ve filed a bug
> for this:
>
> https://bugs.openjdk.java.net/browse/JDK-8170977
>
> Once this bug is fixed, using numeric keys should be roughly as fast as
> using non-numeric ones.
>
> Hannes
>
>
> > Am 09.12.2016 um 04:47 schrie
e
> possible that you exposed some weak spot in our implementation. I’ll have a
> look into what’s going on.
>
> Hannes
>
>
> > Am 08.12.2016 um 00:40 schrieb Jesus Luzon <jlu...@riotgames.com>:
> >
> > Looks like the memory leak is due to the way we wrote our cod
sonably possible?
On Wed, Dec 7, 2016 at 11:23 AM, Jesus Luzon <jlu...@riotgames.com> wrote:
> Yes, it's an array of objects which I'll paste. And yes, I'm just calling
> invokeFunction from many many different threads. I'm also going to go back
> and take a look at all the heap dum
onstrates this behaviour? If so
> I’ll file a bug and dig in. It sounds like an object is being reused
> across invocations and accumulating changes to the property map.
>
> — Jim
>
>
> On Dec 6, 2016, at 5:12 PM, Jesus Luzon <jlu...@riotgames.com> wrote:
>
> With
>
> System.out.println((System.currentTimeMillis() -
>> lastTimestamp)/1000.0);
>
> lastTimestamp = System.currentTimeMillis();
>
> }
>
> }
>
>
On Tue, Dec 6, 2016 at 5:31 AM, Jim Laskey (Oracle) <james.las...@or
s the worst case. A new context per
> thread does much better. A new global per thread is the best while
> remaining thread safe.
>
> Cheers,
>
> — Jim
>
>
>
>
>
> On Dec 6, 2016, at 8:45 AM, Jesus Luzon <jlu...@riotgames.com> wrote:
>
> Hey folks,
&g
s hasn't netted me any results yet.
Thanks.
Jesus Luzon
10 matches
Mail list logo
