[
https://issues.apache.org/jira/browse/TINKERPOP-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732377#comment-17732377
]
ASF GitHub Bot commented on TINKERPOP-2958:
-------------------------------------------
kenhuuu commented on PR #2090:
URL: https://github.com/apache/tinkerpop/pull/2090#issuecomment-1590514662
VOTE +1
The same kind of issue exists with the HttpGremlinEndpointHandler
(`GremlinExecutor.eval` as Valentyn mentioned) and the UnifiedHandler but to a
far lesser degree so I think it is fine to keep those as is. The `Context`
object is much larger which is why it affects these two processors much more.
> 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)
