Issue Details (XML | Word | Printable)

Key: BAM-950
Type: Bug Bug
Status: Resolved Resolved
Resolution: Resolved Locally
Priority: Major Major
Assignee: Unassigned
Reporter: Andrew Herbert
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Bamboo

Out of memory error while processing Clover 2.0a4 results

Created: 01/Mar/07 11:00 PM   Updated: 18/Mar/07 08:02 PM
Component/s: Build Process
Affects Version/s: 1.0
Fix Version/s: 1.1

Time Tracking:
Not Specified

File Attachments: 1. Text File bamboo-clover-build-error.txt (4 kB)
2. Text File jmap -heap.txt (1 kB)

Environment:
Apache Tomcat/5.5.20. Java(TM) SE Runtime Environment (build 1.6.0-b105), Java HotSpot(TM) Server VM (build 1.6.0-b105, mixed mode). Solaris 10 SPARC.
Clover 2.0a4.

Internal Priority: 2. High
Participants: Andrew Herbert and Edwin Wong [Atlassian]
Since last comment: 1 year, 24 weeks, 4 days ago
Number of comments: 4
Labels:


 Description  « Hide
Bamboo's build process fails while Bamboo is processing Clover results (from a 2.0a4 beta version of Clover). Stacktrace attached. The clover XML results file is reasonably large (14 MB), which may be a factor.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Andrew Herbert added a comment - 02/Mar/07 12:45 AM
jmap -heap output also attached.

Edwin Wong [Atlassian] added a comment - 05/Mar/07 02:27 AM
Andrew,

Would you know what permGen size you are running on? I am guessing you can alleviate this problem (to some degree) by turning up your permGen size?

Cheers,
Edwin


Andrew Herbert added a comment - 15/Mar/07 12:31 AM
Hi Edwin,

I had upped the maximum heap size (-Xms4096M) to try to address this.
Have now increased from the 84M default up to 256M
(-XX:MaxPermSize=256M). It's been working well with this MaxPermSize
setting.

thanks,
Andrew


Edwin Wong [Atlassian] added a comment - 18/Mar/07 08:02 PM
Andrew,

Good to hear. We have also set the default perm-gen size up since the 1.0.1 release to prevent this issue.

I'll resolve this issue for now. Please let us know if you have any other issues, comments, or feedback.

Regards,
Edwin