StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POMemory leak in MongoDB cursor (OutOfMemory)?
primarykey
Id
18684598
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-09-08T14:05:57.343
FavoriteCount
0
LastActivityDate
2013-09-10T18:56:34.750
LastEditDate
LastEditorUserId
0
OwnerUserId
187141
ParentId
0
PostTypeId
1
Score
2
ViewCount
2789
LastEditorDisplayName
text
Body
This is how I'm reading my large MongoDB table (every object has very big chunks of data in its attributes): <pre><code>DBCursor cursor = collection.find(/* my query */); while (cursor.hasNext()) { DBObject object = cursor.next(); doSomething(object); // no data stays in memory } cursor.close(); </code></pre> I'm getting: <pre><code>java.lang.OutOfMemoryError: Java heap space at java.lang.StringCoding$StringDecoder.decode(Unknown Source) at java.lang.StringCoding.decode(Unknown Source) at java.lang.String.<init>(Unknown Source) at org.bson.BasicBSONDecoder$BSONInput.readUTF8String(BasicBSONDecoder.java:463) at org.bson.BasicBSONDecoder.decodeElement(BasicBSONDecoder.java:155) at org.bson.BasicBSONDecoder._decode(BasicBSONDecoder.java:79) at org.bson.BasicBSONDecoder.decode(BasicBSONDecoder.java:57) at com.mongodb.DefaultDBDecoder.decode(DefaultDBDecoder.java:56) at com.mongodb.Response.<init>(Response.java:83) at com.mongodb.DBPort.go(DBPort.java:124) at com.mongodb.DBPort.call(DBPort.java:74) at com.mongodb.DBTCPConnector.innerCall(DBTCPConnector.java:286) at com.mongodb.DBTCPConnector.call(DBTCPConnector.java:257) at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:310) at com.mongodb.DBApiLayer$MyCollection.__find(DBApiLayer.java:295) at com.mongodb.DBCursor._check(DBCursor.java:368) at com.mongodb.DBCursor._hasNext(DBCursor.java:459) at com.mongodb.DBCursor.hasNext(DBCursor.java:484) </code></pre> Exception is thrown after 200-300 objects are processed. Does the driver holds data in memory? I'm using <pre><code><dependency> <groupId>org.mongodb</groupId> <artifactId>mongo-java-driver</artifactId> <version>2.10.1</version> </dependency> </code></pre>
Tags
<java><mongodb>
Title
Memory leak in MongoDB cursor (OutOfMemory)?
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USyegor256
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POMemory leak in MongoDB cursor (OutOfMemory)?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COI would have thought the cursor does not keep reference to previous objects (the code is open source: you could have a look at the implementation). Possibly related: http://stackoverflow.com/questions/13531004/java-outofmemoryerror-strange-behaviour
 singulars
 PostPostId
 POMemory leak in MongoDB cursor (OutOfMemory)?
 UserUserId
 USassylias

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.