I have two questions about a Wineskin wrapper's functionality:
__First__:
I've noticed while attaching ===any=== Wineskin wrapper to Instruments, I get a 32-byte memory leak. Something along the lines of:
-WineskinLauncher is responsible
-an NSCFString
-adress 0x10235c0d0 (don't know how this can help)
-responsible frame is -[WineStart setVdResolution:]
This is just theoretical, I don't know for sure if this can/may happen: although not a real problem, even for 1GB Macs, you may get memory problems if you consider using a server that launches (and closes after a while) a certain Wineskin wrapper every few minutes. The only way to avoid having the memory all clogged up is programing a purge every now and then.
__Second__:
Can the executable name at wswine.bundle/bin (for example: MyCoolWrapper26401537Wine) be changed to something else, as along as the Info.plist and other files referring to it (wine, wineserver files) are also changed according to the new name I give it?
↧