On Jun 6, 2017, at 5:58 PM, Stephan Beal <[email protected]> wrote: > > If you leave quotes off of the property names, it's not json
Yes, but that’s only one of the three problems here. The other two are: 1. It should diagnose the error correctly. (The error has nothing to do with memory allocation.) 2. It should return the error message via JSON to the client, not print it on the console. The JSON API is most likely to be used in cases where the called Fossil instance is running in the background, with stdio detached. > Why that shows up as a response allocation error, i can't say off hand. From what debugging I did, it’s because the parsing failure caused most of the fields of g.json to be unset, which causes multiple levels of NULL to be returned, which the scream-and-die code misinterprets as given. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
