Bug 443304 - Unison fails with "Out of memory" error
Summary: Unison fails with "Out of memory" error
Keywords:
Status: CLOSED DUPLICATE of bug 441685
Alias: None
Product: Fedora
Classification: Fedora
Component: unison227
Version: 9
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Stephen Warren
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-20 13:32 UTC by Manuel Morales
Modified: 2008-05-14 11:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-14 11:34:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Manuel Morales 2008-04-20 13:32:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b5) Gecko/2008041301 Fedora/3.0-0.54.beta5.fc9 Firefox/3.0b5

Description of problem:
When synchronizing directories with a large number of files, I get an out of memory error. Running with "-debug all" shows the following:

Growing heap to 10132k bytes
Growing page table to 34357992238 entries
No room for growing page table
Uncaught exception Out of memory

Version-Release number of selected component (if applicable):
unison227-2.27.57-8.fc9.x86_64

How reproducible:
Always


Steps to Reproduce:
1. Start unison
2. Synchronize directories
3. Out of memory and crash

Actual Results:


Expected Results:


Additional info:

Comment 1 John Poelstra 2008-04-21 17:28:24 UTC
thanks for reporting this bug

Comment 2 Dan Winship 2008-05-13 00:09:15 UTC
This only happens with the x86_64 package; if you install unison227.i386 instead
it works fine. So it's some sort of 64-bit uncleanliness.


Comment 3 Bug Zapper 2008-05-14 09:47:02 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Stephen Warren 2008-05-14 11:34:05 UTC

*** This bug has been marked as a duplicate of 441685 ***


Note You need to log in before you can comment on or make changes to this bug.