- --
Viewing Issue Advanced Details
[ Jump to Notes ]
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
09045 | Misc. | Minor | Always | 1 day ago | 1 day ago |
Tester | Firewave | View Status | Public | Platform | MAME (Self-compiled) |
Assigned To | Resolution | Duplicate | OS | Linux (64-bit) | |
Status [?] | Closed | Driver | |||
Version | 0.272 | Fixed in Version | Build | 64-bit | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 09045: memory leak using -video bgfx | ||||
Description |
Running with `video bgfx` LeakSanitizer (included in AddressSanitizer and enabled by default) will report several leaks from the bgfx code. I attached a log with the messages (the ones with incomplete stacktraces can probably be ignored). This can probably be reproduced with valgrind as well. |
||||
Steps To Reproduce | -video bgfx -bgfx_path bgfx pacman | ||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | |||||
Attached Files
|
|||||
Relationships
|
Notes
1
No.22648
Firewave Senior Tester
1 day ago
edited on: 1 day ago |
This was accidentally double-posted because I originally attached a file with an extension (.log) was was not allowed. It was not obvious from that error that the ticket had been created even though I was shown a big error message. |
---|