vkd3d-shader: Fix a couple of memory leaks.
2 unresolved threads
2 unresolved threads
Merge request reports
Activity
IMO, cleaning memory leaks has the benefit of clearing valgrind output, which I think can make real errors more detectable.
Yeah, that's precisely how I got there.
Also, it seems that somebody cared about memory leaks at some point, because memory is freed on many code paths (both exceptional and not). But others are missing.
717 717 int ret; 718 718 719 719 if (!parse_command_line(argc, argv, &options)) 720 return 1; 720 goto done; 721 721 722 722 if (options.print_help) 723 723 { 724 724 print_usage(argv[0]); 725 return 0; 725 fail = 0; added 6 commits
-
494507bb...d38221bd - 3 commits from branch
wine:master
- 896fc0c2 - vkd3d-compiler: Exit the main function through a common code path.
- 8b11b4b3 - vkd3d-compiler: Free compilation options (Valgrind).
- cc72a8d3 - vkd3d-shader/spirv: Free binary SPIR-V code (Valgrind).
Toggle commit list-
494507bb...d38221bd - 3 commits from branch
Please register or sign in to reply