Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory leak occurred (in StrictMode) #32

Closed
allsoft777 opened this issue May 12, 2015 · 2 comments
Closed

Memory leak occurred (in StrictMode) #32

allsoft777 opened this issue May 12, 2015 · 2 comments
Projects

Comments

@allsoft777
Copy link

Hello. I'm a software engineer developing an android application.
First above all, i'd like to say "thank you" for your support.
I've developed all of things related with the ical4j module.

But, i got an issue for memory leak when composing an event.
It was occurred in TimeZoneRegistryFactory.
I guess the stream is leaked..because the thread is un-safe.

Is there any workaround for this?
(i.e options..)

Thanks.

05-12 10:48:08.808 952-967/com.android.calendar E/StrictMode﹕ A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.
java.lang.Throwable: Explicit termination method 'end' not called
at dalvik.system.CloseGuard.open(CloseGuard.java:184)
at java.util.zip.Inflater.(Inflater.java:82)
at java.util.zip.ZipFile.getInputStream(ZipFile.java:331)
at java.util.jar.JarFile.getInputStream(JarFile.java:390)
at libcore.net.url.JarURLConnectionImpl.getInputStream(JarURLConnectionImpl.java:222)
at java.net.URL.openStream(URL.java:470)
at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:444)
at net.fortuna.ical4j.util.ResourceLoader.getResourceAsStream(ResourceLoader.java:77)
at net.fortuna.ical4j.model.TimeZoneRegistryImpl.(TimeZoneRegistryImpl.java:76)
at net.fortuna.ical4j.model.DefaultTimeZoneRegistryFactory.createRegistry(DefaultTimeZoneRegistryFactory.java:48)
at com.android.calendar.icalendar.encoder.BaseEventEncoder.addDateTimeProperty(BaseEventEncoder.java:169)

@benfortuna
Copy link
Member

Thanks for the feedback. I think I have a fix for the issue in this pull request:

#33

I'll try to get it merged and deployed in a new release shortly.

@benfortuna benfortuna added this to Needs triage in Android via automation Nov 24, 2018
@benfortuna
Copy link
Member

Closing issue as fixed. Feel free to reopen if problem still manifests.

Android automation moved this from Needs triage to Closed Nov 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Android
  
Closed
Development

No branches or pull requests

2 participants