[
https://issues.apache.org/jira/browse/TINKERPOP-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731737#comment-17731737
]
ASF GitHub Bot commented on TINKERPOP-2958:
-------------------------------------------
lyndonbauto commented on PR #2090:
URL: https://github.com/apache/tinkerpop/pull/2090#issuecomment-1587887574
> Can similar problem occur in `GremlinExecutor.eval`?
I looked and as far as I can tell, this issue is limited to the two places I
fixed it, however I am not well versed with this part of the gremlin code base
so I may be wrong.
> Are you planning to open separate PR for 3.5 and 3.6?
This code is identical in 3.5 and 3.6 so my plan was to merge this to
3.5-dev then merge 3.5-dev into 3.6-dev. I just noticed I was pointed at master
but meant to be pointed at 3.5-dev in this PR. @spmallette is this the right
merging strategy?
> ScheduledExecutorService for timeouts are never cancelled
> ---------------------------------------------------------
>
> Key: TINKERPOP-2958
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2958
> Project: TinkerPop
> Issue Type: Bug
> Components: server
> Affects Versions: 3.6.3, 3.6.4
> Reporter: Lyndon Bauto
> Assignee: Lyndon Bauto
> Priority: Major
>
> A scheduled task was added to timeout a request in the future.
>
> This task is not cancelled when the request is completed before the timeout.
> With a long timeout, this can lead to extreme memory usage (~1 GB growth per
> minute on my laptop with my graph implementation).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
