couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Beano (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1490) Problems with views on large documents JSONs
Date Sun, 07 Apr 2013 23:33:15 GMT


Beano commented on COUCHDB-1490:

I had the same problem on Ubuntu 12.10 with js 1.8.5. I think I've got a fix/patch. I found
that adjusting the size of the javascript runtime via JS_NewRuntime fixed it for me. It is
currently hard-coded to 64 megs. 

I added a command-line flag to couchjs with reference to this similar issue:

I've only compiled and tested against js 1.8.5. I would be happy to contribute a patch but
I'd need some guidance on how to go about doing this.
> Problems with views on large documents JSONs
> --------------------------------------------
>                 Key: COUCHDB-1490
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Mac Os x 10.6.8, intel Architecture (x86_64), 8Gb of Ram, Erlang
R15B01 (erts-5.9.1)
>            Reporter: Francesco
>         Attachments: error.log
> Hi,
> i run a couchdb server (v1.2.0) over a mac (intel architecture, 8gb of ram,
> os x version 10.6.8) installed with brew.
> The server itself is used as a storage of big jsons (example:
and ) for
a tiny uni project.
> When we load more than 3 of these jsons, all the map functions (we created to retrieve
documents besides a simple get by id) does not work.
> A typical map is:
> function(doc){if(doc.TITLE.title.match('.*INSULIN.*') !== null) emit(doc.ID,
> doc);}
> but even a
> function(doc){emit(doc.ID, doc.ID)}
> cease to work.
> while when there are just 3 or 2 jsons in the database they work just fine. I tried increasing
the stack for couchjs (1gb now, going over 1gb doesn't work it seems), increasing limits for
files (4096), increasing timeout for processes but in the end i don't get any results and
only a (Error:
> os_process_error {exit_status,0}) from the db.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message