-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crashing when the data is invalid json string. #125
Comments
Can you be more specific? Please provide the json, the crash log and messages in the console |
For example, you can insert a simple json first:
Then update it:
please note, I type by mistake with Process: MongoHub [23915] Date/Time: 2014-06-14 19:41:27.354 +0800 Sleep/Wake UUID: 33376F43-1286-449C-88BA-7FB0DAD2181C Crashed Thread: 1 Dispatch queue: NSOperationQueue Serial Queue Exception Type: EXC_CRASH (SIGABRT) Application Specific Information: Application Specific Backtrace 1: Thread 0:: Dispatch queue: com.apple.main-thread Thread 1 Crashed:: Dispatch queue: NSOperationQueue Serial Queue Thread 2:: Dispatch queue: com.apple.libdispatch-manager Thread 3: Thread 4:: com.apple.NSURLConnectionLoader Thread 5: Thread 6:: com.apple.CFSocket.private Thread 7: Thread 1 crashed with X86 Thread State (64-bit): Logical CPU: 0 Binary Images: External Modification Summary: VM Region Summary: REGION TYPE VIRTUAL |
There is probably same bug while updating document. If I set the following string to update field
mongohub will crash, but if I change it to
it will work. And console output is here: 21/07/14 17:48:16,386 MongoHub[48264]: *********************** class (null) key � And this is with version 2.7b6 |
Thanks for the stack trace. It doesn't look like the same bug. |
Can you reproduce this issue all the time? |
Yes, I can. And of course query field can't be blank, I tested with empty query field {} |
This is a totally different bug from the first description. This might have implication data wrote in the database. It has been introduced in 2.7. And it should be fixed in 2.7b7. Sorry for the problem. Let me know if it works now. |
No problem at all. I am glad to help. Now it seems to work without problem, thanks. |
Great! I'm happy to hear that. If you want, you can open another issue about the fact the fields cannot be empty. |
Should be fixed in 3.0. You can verify this issue, and close it. |
Crashing when the data is invalid json string.
The text was updated successfully, but these errors were encountered: