Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[atari][media] Mem leak in DiskTypeXEX. #642

Open
tschak909 opened this issue Jul 26, 2023 · 0 comments
Open

[atari][media] Mem leak in DiskTypeXEX. #642

tschak909 opened this issue Jul 26, 2023 · 0 comments
Labels
memleak Memory Leak

Comments

@tschak909
Copy link
Collaborator

Looks like when an XEX is mounted, some next level heap corruption occurs:

22:11:41.416 > CF: 70 d6 02 00 49
22:11:41.416 > sioFuji::sio_process() called
22:11:41.421 > ACK!
22:11:41.421 > disk UNMOUNT
22:11:41.421 > Mounting lobby server
22:11:41.421 > Resolving hostname "tnfs.fujinet.online"
22:11:41.596 > Resolved to address 104.248.6.55
22:11:41.596 > TNFS mount tnfs.fujinet.online[104.248.6.55]:16384
22:11:41.653 > TNFS mount successful. session: 0x3876, version: 0x0102, min_retry: 1000ms
22:11:41.654 > vfs_tnfs_register "/tnfs0x3ffcde20" @ 0x3ffcde20 = 0 "ESP_OK"
22:11:41.657 > opening lobby.
22:11:41.708 > TNFS open file: "/ATARI/_lobby.xex" (0x0001, 0x01b6)
22:11:41.762 > File opened, handle ID: 0, size: 13156, pos: 0
22:11:41.762 > disk MOUNT
22:11:41.762 > XEX MOUNT
22:11:41.765 > load_firmware '/picoboot.bin'
22:11:41.928 > load_firmware file size = 384
22:11:41.928 > mounted XEX with 384-byte bootloader; XEX size=0
22:11:41.931 > disk sectors = 720
22:11:41.935 > COMPLETE!
22:11:41.935 > [lib/bus/sio/sio.cpp:255] _sio_process_cmd(): Heap trace follows
22:11:41.936 > 8 allocations trace (100 entry buffer)
22:11:41.937 > 92 bytes (@ 0x3ffdd76c) allocated CPU 1 ccount 0x018f8f38 caller 0x40093c3b:0x40130854
22:11:41.939 > 12 bytes (@ 0x3ffddb90) allocated CPU 1 ccount 0x018fa444 caller 0x4013812d:0x4013088c
22:11:41.940 > 192 bytes (@ 0x3ffefab0) allocated CPU 1 ccount 0x04e1913c caller 0x40138584:0x4013865c
22:11:41.943 > 92 bytes (@ 0x3ffddbac) allocated CPU 1 ccount 0x04ebd2ac caller 0x40093c3b:0x40093f97
22:11:41.944 > 796 bytes (@ 0x3ffefc90) allocated CPU 1 ccount 0x04ec09e8 caller 0x4018ac84:0x401d966f
22:11:41.947 > 836 bytes (@ 0x3ffeffbc) allocated CPU 1 ccount 0x067352fc caller 0x4018ac84:0x400ee7f2
22:11:41.948 > 428 bytes (@ 0x3ffdd954) allocated CPU 1 ccount 0x08cc44a8 caller 0x4009a3c4:0x4008d1d2
22:11:41.950 > 384 bytes (@ 0x3fff0310) allocated CPU 1 ccount 0x08ceab58 caller 0x400f18f6:0x401d7730
22:11:41.953 > 2832 bytes 'leaked' in trace (8 allocations)
22:11:41.953 > total allocations 2240 total frees 2277
@tschak909 tschak909 added the memleak Memory Leak label Jul 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
memleak Memory Leak
Projects
None yet
Development

No branches or pull requests

1 participant