{"action":"opened","issue":{"url":"https://api.github.com/repos/mikeizbicki/ucr-cs100/issues/1396","labels_url":"https://api.github.com/repos/mikeizbicki/ucr-cs100/issues/1396/labels{/name}","comments_url":"https://api.github.com/repos/mikeizbicki/ucr-cs100/issues/1396/comments","events_url":"https://api.github.com/repos/mikeizbicki/ucr-cs100/issues/1396/events","html_url":"https://github.com/mikeizbicki/ucr-cs100/issues/1396","id":68898777,"number":1396,"title":"Leaking memory","user":{"login":"divyanshch","id":5580328,"avatar_url":"https://avatars.githubusercontent.com/u/5580328?v=3","gravatar_id":"","url":"https://api.github.com/users/divyanshch","html_url":"https://github.com/divyanshch","followers_url":"https://api.github.com/users/divyanshch/followers","following_url":"https://api.github.com/users/divyanshch/following{/other_user}","gists_url":"https://api.github.com/users/divyanshch/gists{/gist_id}","starred_url":"https://api.github.com/users/divyanshch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/divyanshch/subscriptions","organizations_url":"https://api.github.com/users/divyanshch/orgs","repos_url":"https://api.github.com/users/divyanshch/repos","events_url":"https://api.github.com/users/divyanshch/events{/privacy}","received_events_url":"https://api.github.com/users/divyanshch/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-16T10:55:43Z","updated_at":"2015-04-16T10:55:43Z","closed_at":null,"body":"When running valgrind should we be trying to fix the memory leaking that is listed as \"possibly lost\" or \"still reachable\"? If yes, what would be the best method to find and free that memory. \r\n\r\nI have been reading some articles and they have said that \"still reachable\" memory is okay since those pointers don't cause any problem that a actual memory leak would cause."}}