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.

Sign up for GitHub

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

Jump to bottom

Memory leak in Map #169

Closed
martinpsk opened this issue Jun 18, 2013 · 2 comments · May be fixed by xhad/scc#81, enterstudio/kibana#83 or 82ndAirborneDiv/kibana#43
Closed

Memory leak in Map #169

martinpsk opened this issue Jun 18, 2013 · 2 comments · May be fixed by xhad/scc#81, enterstudio/kibana#83 or 82ndAirborneDiv/kibana#43
Labels
bug Fixes for quality problems that affect the customer experience

Comments

@martinpsk
Copy link

Hi,

I'm seeing an issue with a Kibana 3 milestone 2 and elasticsearch 0.90.1 setup.

When I add an auto-refresh interval the map seems to keep growing without ever freeing up any space. Trying to gc in chrome didn't help either. It also doesn't seem to matter what query the map is doing.

Here are some heap snapshots. First one is from about 20 seconds afters selecting a 3s auto-refresh.
after_start

Second one is a heap snapshot from chrome after maybe 5 minutes of auto-refreshing:
mem_leak

From the second heap snap you can see that the retained size of the map grew to 135 MB.

I also tried bettermap and map2 and it doesn't seem to affect those two. Tested in chrome 27.0.1453.110 but also seen in firefox.
@rashidkpc rashidkpc added the bug label Feb 24, 2014
@bluepuma77
Copy link

I confirm this issue. Chromium on Raspberry Pi dies ("He is dead, Jim") after 3 hours with 2 maps and 5 minute refresh rate. Now I disabled the 2 maps and it is running for a full day, still memory available.

@spalger
Copy link
Contributor

spalger commented Oct 6, 2014

Closing this since Kibana 4 does not currently have a map, and won't be using the same mapping module that Kibana 3 did.

Thanks!

@spalger spalger closed this as completed Oct 6, 2014
spalger pushed a commit to spalger/kibana that referenced this issue Mar 3, 2016
@simianhacker
Closes elastic#206 - Additions to Sense Knowledge Base
76cc5d6 
- Closes elastic#169 - Add type field to multi_match
- Closes elastic#175 - Adding global autocomplete rules for aliases
- Closes elastic#194 - Adding time_zone to date_histogram agg
- Closes elastic#199 - Removed multi_field type and added copy_to
- Closes elastic#170 - Add _bunch endpoint
- Closes elastic#174 - Adding _search/template endpoint
w33ble added a commit to w33ble/kibana that referenced this issue Sep 13, 2018
@w33ble
Fix: History elements update on history change (elastic#169)
75f3a32 
* chore: refactor some of the code

use shorter syntax for some things, and just generally reduce the line count... less lines is good, right?

* fix: initialize workpad on history restore

because the resolved args are cleared, we need to trigger a workpad re-init so they get repopulated

this is admittedly an ugly fix, and i've added some TODO lines to indicate what we should change
@snyk-bot snyk-bot mentioned this issue Nov 15, 2022
Open
@enterstudio enterstudio mentioned this issue Nov 28, 2022
Open
@xhad xhad mentioned this issue Feb 2, 2024
Open
@enterstudio enterstudio mentioned this issue Feb 3, 2024
Open
@82ndAirborneDiv 82ndAirborneDiv mentioned this issue Feb 3, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience
Projects
None yet
Milestone
No milestone
4 participants
@rashidkpc @spalger @martinpsk @bluepuma77