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 when navigating between pages located in separate files (JQM 1.4 final) #6816

Closed
wauwau0977 opened this Issue Dec 20, 2013 · 3 comments

Comments

Projects
None yet
3 participants
@wauwau0977

wauwau0977 commented Dec 20, 2013

Hi

JQM leaves some detached DOM objects. Depending on the structure of the page this may cause a significant memory leak.

Attached is the simplest case i can imagine. It will reproduce the behaviour. Also attached some screenshot with Google Chrome Profiler. Please switch 10x between page1 and page 2 to see an increase of about 100k...

This can be reproduced with JQuery 1.x and 2.x.

Our application is much more complex then the example, so we see rather big memory increase. Important: It seems as the demo i attached has just one simple leak. Unfortunately we see in our real application much more (since we use more widgets and events).

If you need more info, please ask...

The working demo that reproduces the behaviour can be downloaded from:
http://mindalyze.com/develop/JQueryMobile14MemoryLeak.zip (showcase folder)

chrome_devtools_memory_snapshot

Best regards,
Patrick Heusser

@arschmitz

This comment has been minimized.

Show comment
Hide comment
@arschmitz

arschmitz Jan 2, 2014

Member

Thank you for reporting this issue. For us to look into their further can you please see our contributing guidelines at https://github.com/jquery/jquery-mobile/blob/master/CONTRIBUTING.md and create a jsbin test page which reproduces the issue. For now i'm going to close this as incomplete. We will reopen when the requested information is provided.

Member

arschmitz commented Jan 2, 2014

Thank you for reporting this issue. For us to look into their further can you please see our contributing guidelines at https://github.com/jquery/jquery-mobile/blob/master/CONTRIBUTING.md and create a jsbin test page which reproduces the issue. For now i'm going to close this as incomplete. We will reopen when the requested information is provided.

@arschmitz arschmitz closed this Jan 2, 2014

@wauwau0977

This comment has been minimized.

Show comment
Hide comment
@wauwau0977

wauwau0977 Jan 3, 2014

Thanks for having a look at it... I completely understand, that you like to see the bug in standard view like jsbin.

i tried to create a jsbin version, unfortunately with multiple pages when JQM tries to load the new page, it gets a JSON object from jsbin...

http://jsbin.com/IVImOfa/latest/quiet

the zip i attached already contains a nice test setup, it just needs to be extracted and clicked to run... it's even cleaner, since it's "pure"...

please give it a look, we really struggle with the memory leak here...

regards,
patrick

wauwau0977 commented Jan 3, 2014

Thanks for having a look at it... I completely understand, that you like to see the bug in standard view like jsbin.

i tried to create a jsbin version, unfortunately with multiple pages when JQM tries to load the new page, it gets a JSON object from jsbin...

http://jsbin.com/IVImOfa/latest/quiet

the zip i attached already contains a nice test setup, it just needs to be extracted and clicked to run... it's even cleaner, since it's "pure"...

please give it a look, we really struggle with the memory leak here...

regards,
patrick

@arschmitz arschmitz reopened this Jan 16, 2014

arschmitz added a commit that referenced this issue Jan 22, 2014

AnimationComplete: Add transition, fallbacks and remove memory leaks
Also no its own module including support tests for animations and
transitions

Fixes gh-5156
Fixes gh-6816
Fixes gh-6697
Fixes gh-6895
Fixes gh-6148

arschmitz added a commit that referenced this issue Feb 12, 2014

AnimationComplete: Add transition, fallbacks and remove memory leaks
Also no its own module including support tests for animations and
transitions

Fixes gh-5156
Fixes gh-6816
Fixes gh-6697
Fixes gh-6895
Fixes gh-6148
Closes gh-7001

@arschmitz arschmitz closed this in 749c78e Feb 12, 2014

@voronianski

This comment has been minimized.

Show comment
Hide comment
@voronianski

voronianski Jul 11, 2014

@arschmitz @wauwau0977 is it possible to prevent this memory leak without updating to 1.4?

voronianski commented Jul 11, 2014

@arschmitz @wauwau0977 is it possible to prevent this memory leak without updating to 1.4?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment