00686: viper.c, gaelco3d.c: [debug] Memory Leaks

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
00686	Misc.	Minor	Always	Feb 1, 2008, 20:52	Feb 10, 2008, 05:44

Tester	Firewave	View Status	Public	Platform
Assigned To		Resolution	Fixed	OS
Status [?]	Resolved			Driver
Version	0.119u3	Fixed in Version	0.122u4	Build
		Fixed in Git Commit		Github Pull Request #

Summary	00686: viper.c, gaelco3d.c: [debug] Memory Leaks
Description	Several memory leaks happened with viper.c and others (Updated in 0.122): --- memory leak warning --- allocation #003415, 131072 bytes (src/emu/cpu/x86drc.c:251) allocation #003414, 131072 bytes (src/emu/cpu/x86drc.c:251) allocation #003164, 16 bytes (src/osd/windows/winwork.c:164) allocation #003163, 68 bytes (src/osd/windows/winwork.c:132) allocation #002588, 4096 bytes (src/emu/cpu/x86drc.c:108) allocation #002587, 4096 bytes (src/emu/cpu/x86drc.c:103) allocation #002586, 131072 bytes (src/emu/cpu/x86drc.c:95) allocation #002585, 131072 bytes (src/emu/cpu/x86drc.c:94) a total of 532564 bytes were not free()'d Seems like the winwork.c memory leaks are heppeing with drivers using the voodoo.c. gaelco3d.c: radikalb leaks dozens of this: allocation #004272, 32 bytes (src/osd/windows/winwork.c:350) Added in 0.120u1: polynew.c, using viper.c: boxingm as example: allocation #003161, 2162688 bytes (src/emu/video/polynew.c:170) allocation #003160, 3072 bytes (src/emu/video/polynew.c:168) allocation #003159, 2408448 bytes (src/emu/video/polynew.c:155) allocation #003158, 256 bytes (src/emu/video/polynew.c:153) allocation #003157, 184 bytes (src/emu/video/polynew.c:146)
Steps To Reproduce
Additional Information
Github Commit

Flags	Debug build specific
Regression Version
Affected Sets / Systems	viper.c, gaelco3d.c

Attached Files