[CORE] Change mmap flag judgment in getMmapped#4003
Conversation
Change getMmapped to strictly check MEM_MMAP flag instead of MEM_ALLOCATED bitmask.
|
Have you tested other things with this pathc, espcialy 32bits apps/games? |
I’m going to test box32 apps and provide more accurate change descriptions. |
I created a test case to reproduce the issue I encountered when running x86_64 Electron on RISC-V Linux via Box64 (command: When I believe using only the
In my opinion, the most robust solution would be to explicitly track every memory block allocated through the x86_64 custom memory allocator. However, this approach could introduce performance overhead. What would you recommend as the proper fix here?
|
|
Mmmm, you have a x86_64 custom allocator that use |
Change
getMmappedto strictly checkMEM_MMAPflag instead ofMEM_ALLOCATEDbitmask.I found that some memory allocated via native
mallocis also registered inmapallmemwith theMEM_ALLOCATEDflag, and later released through custom free routines.