You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "Robert Kowalski (JIRA)" <ji...@apache.org> on 2016/09/11 13:00:23 UTC

[jira] [Commented] (COUCHDB-3141) Default Mango Query has browser memory leak

    [ https://issues.apache.org/jira/browse/COUCHDB-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15481720#comment-15481720 ] 

Robert Kowalski commented on COUCHDB-3141:
------------------------------------------

From thinking about it it seems that the prefilled catch-all selector which translates to SELECT * from $db returns all those docs and the fauxton wants to render them.

Have to verify now

> Default Mango Query has browser memory leak
> -------------------------------------------
>
>                 Key: COUCHDB-3141
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-3141
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Fauxton
>            Reporter: Jan Lehnardt
>
> I have a database with just over 20k docs replicated into a 2.0.0 release candidate. When I navigate to the Mango screen and leave everything on default, and then press the “Run Query” button, it takes maybe 30 seconds before that browser tab eats up all the available RAM, I’ve confirmed this in Safari, Chrome and Firefox on latest stable Mac OS X.
> I don’t know enough about Mango and whether the defaults for a query are in any way useful, I just tried hitting a button to see what happens, and a memory leak is not what I’ve expected ;)
> CouchDB looks like its doing fine, it’s the Browser that runs out of memory *quickly* (in one instance 20GB in ~1 minute)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)