Suspected memory leak in PersistentTranslationService/GoogleTranslatorBackend
Description
Environment
None
Activity
Show:
Ready for Release
Details
Details
Assignee
Sean Flanigan
Sean FlaniganReporter
Sean Flanigan
Sean FlaniganSprint
None
Priority

More fields
Time tracking
More fields
Time trackingCreated 27 August 2018 at 08:39
Updated 30 August 2018 at 03:06
Resolved 30 August 2018 at 03:06
@Dependent
Instances have to be destroyed[1], but only the@Dependent
ones[2], and yet there is no easy way of identifying them (short of using WeldInstance[3]).We could use WeldInstance, but it makes the code more complex, so I suggest we just ensure the TranslatorBackends are all properly scoped (eg
@ApplicationScoped
).[1] https://blog.akquinet.de/2017/01/04/dont-get-trapped-into-a-memory-leak-using-cdi-instance-injection/
[2] https://developer.jboss.org/thread/252712
[3] http://weld.cdi-spec.org/news/2016/05/18/enhanced-instance/