[SERVER-418] `mongo`'s reproducible crash. Created: 12/Nov/09  Updated: 12/Jul/16  Resolved: 13/Nov/09

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 1.1.1
Fix Version/s: 1.1.3

Type: Bug Priority: Minor - P4
Reporter: gf Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

FreeBSD


Participants:

 Description   

> db.btswarm.find();
decode failed. probably invalid utf-8 string [-/---?--?-?---C-]
why: TypeError: malformed UTF-8 character sequence at offset 0
terminate called after throwing an instance of 'mongo::UserException'
what(): invalid utf8
Fri Nov 13 02:07:29 mongo got signal 6 (Abort trap: 6), stack trace:
Bus error: 10 (core dumped)



 Comments   
Comment by Eliot Horowitz (Inactive) [ 13/Nov/09 ]

at least that bug has been fixed by 1.1.3
i verified that the bug was in 1.1.1 and not in 1.1.3

Comment by gf [ 13/Nov/09 ]

1. It contained random bytes in fields of type string. Now I've replaced 'string' to 'bindata' and it causes no exceptions. Throwing exception for bad strings is OK, but segfault is ugly.
2. Segfault occurs when many others exceptions occurs:

> db.btswarm.update(1,2,3);
Fri Nov 13 22:08:10 User Exception 2nd param to update has to be an object
terminate called after throwing an instance of 'mongo::UserException'
what(): 2nd param to update has to be an object
Fri Nov 13 22:08:10 mongo got signal 6 (Abort trap: 6), stack trace:
Bus error: 10 (core dumped)

Comment by Eliot Horowitz (Inactive) [ 12/Nov/09 ]

can you attach a mongodump of a collection that causes this?

Generated at Thu Feb 08 02:54:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.