[SERVER-7496] Mongo.exe client crashes when username of home directory contains a unicode character Created: 28/Oct/12 Updated: 02/Aug/18 Resolved: 18/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 2.2.1 |
| Fix Version/s: | 2.5.0 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Ronan O'Brien | Assignee: | Gregory McKeon (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | Windows | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 7 |
||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
When connecting with the client the first time, everything works ok. When I disconnected, and reconnected, I got the error below. Deleting the existing .mongo.js is one (drastic) workaround.
|
| Comments |
| Comment by auto [ 18/Mar/13 ] |
|
Author: {u'date': u'2013-03-18T14:27:51Z', u'name': u'Tad Marshall', u'email': u'tad@10gen.com'}Message: In Windows, read Unicode environment variables for HOMEDRIVE and HOMEPATH, |
| Comment by Tad Marshall [ 28/Oct/12 ] |
|
Hi Ronan, I've duplicated your problem. Actually, it was a little worse for me; the filename wasn't even displayed correctly in my test. There are some known shortcomings in MongoDB's handling of non-ASCII text on the command line in Windows, and I've linked some related issues. Your issue is distinct because the non-ASCII text wasn't specified on the command line, it was derived from the user account you were using. There is an additional problem; even if the path to the file is specified on the command line, it still doesn't work because the shell converts the command line text to UTF-8 but doesn't translate it into UTF-16 (Windows Unicode) before using it. The workaround you mentioned is probably the easiest one until we fix this. Tad |