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

Sam Stokes commented on COUCHDB-564:
------------------------------------

I have the same issue in Chrome on Linux (x86_64) - test suite runs fine up 
until view_collation, then hangs indefinitely.  (The Chrome process for the tab 
running the tests also seems to gobble up around a GB of RAM.)  All tests run 
fine in Firefox 3.5 on the same OS.

CouchDB version: 0.10.1 release tarball.
Chrome version: 4.0.302.2 dev
OS version: Ubuntu 9.04 x86_64

I compiled CouchDB from the tarball using the Javascript library from XULRunner 
1.9.1.7.  I used the following commands:

LD_RUN_PATH=/usr/lib/xulrunner-1.9.1.7 ./configure 
--with-js-lib=/usr/lib/xulrunner-devel-1.9.1.7/lib/ 
--with-js-include=/usr/lib/xulrunner-devel-1.9.1.7/include 
--prefix=/home/sam/packages/apache-couchdb-0.10.1

LD_RUN_PATH=/usr/lib/xulrunner-1.9.1.7 make -j3

> view_collation and view_collation_raw tests hang Chrome (Dev Channel, OS X) 
> browser
> -----------------------------------------------------------------------------------
>
>                 Key: COUCHDB-564
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-564
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Test Suite
>    Affects Versions: 0.11
>         Environment: OS X 10.6.1, Macbook Pro, 64 bit, Core2Duo; Google 
> Chrome Dev Channel Release 4.0.229.1; CouchDB tr...@833219
>            Reporter: Glenn Rempe
>
> When running the test suite in the Chrome browser on OS X all tests pass 
> until the view_collation test is reached.  It begins running but hangs the 
> browser and pegs the CPU.  Eventually the specific browser process (specific 
> tab) will need to be killed.
> This also happens if either the view_collation or view_collation_raw tests 
> are run individually.
> All of the tests after view_collation and view_collation_raw run cleanly when 
> run manually later so it appears that only these two cause trouble.
> Nothing is shown in the developer tools console in Chrome.
> The same test suite runs clean all the way through when run immediately after 
> in a Safari 4.0.3 browser without any restart of CouchDB required.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to