Side navigation
#10407 closed bug (invalid)
Opened October 03, 2011 04:43AM UTC
Closed October 25, 2011 07:57AM UTC
memory leak
| Reported by: | lexerq@gmail.com | Owned by: | lexerq@gmail.com |
|---|---|---|---|
| Priority: | undecided | Milestone: | None |
| Component: | unfiled | Version: | 1.3.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
I create an element with the context menu.
When I create html element tr:
var newTr = jQuery('<tr oncontextmenu="return openMyMenu();"></tr>');
I have a memory leak.
But, when I create html element tr with this method:
var newTr = document.createElement('tr');
newTr.oncontextmenu = openMyMenu;
I don't have a memory leak.
What this is?
It is my error? Or it is bug in jQuery?
Attachments (0)
Change History (6)
Changed October 03, 2011 04:50AM UTC by comment:1
| owner: | → lexerq@gmail.com |
|---|---|
| status: | new → pending |
Changed October 03, 2011 05:07AM UTC by comment:2
| status: | pending → new |
|---|
Data is updated every 15 seconds. Every 7 minutes browser consumes 50 MB of RAM.
I understand that this is a bad argument, but it's all there is.
Changed October 03, 2011 12:44PM UTC by comment:3
We'll need some additional evidence to avoid this ticket from being closed. At minimum, could you supply us with a complete test case on jsFiddle.net that we can evaluate ourselves to check if the behaviour can be reproduced?
Changed October 07, 2011 12:35AM UTC by comment:4
| status: | new → pending |
|---|
We definitely need a test case before we can continue.
Changed October 10, 2011 10:45AM UTC by comment:5
The code is very large. I will try to reproduce the memory leak using a similar code and post on jsfiddle.net
Changed October 25, 2011 07:57AM UTC by comment:6
| resolution: | → invalid |
|---|---|
| status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Can you provide some evidence of this "memory leak"?