4 ms·
Note that there are downsides with this method: - the startup time increases - if you run several instances of an app, they consume more memory because code u
by codedokode 11y ago
Note that there are downsides with this method:
- the startup time increases
- if you run several instances of an app, they consume more memory because code uses anon mapping instead of file mapping
- the whole executable file is loaded to memory at startup
- modeless 11y agoA bigger downside: various virus scanners flag UPX-packed executables as suspicious.
- fileoffset 11y agoNot entirely true. Most AV will only flag 'non-standard' UPX packed executables as suspicious. Standard UPX packed binaries are easily unpacked by the scanner and the contents scanned without notifying user.
- pilif 11y agoIt's anecdotal of course, but a small application of ours went from about one false-positive per month to no false positive in over a year when I stopped UPX packing it.
- SyneRyder 11y agoMore anecdata here, but I've experienced the same thing as well (not quite as frequent as one false-positive a month though). UPX just seems to occasionally trip up the antivirus heuristic scans until you can get your application whitelisted.
- thrownaway2424 11y ago"whole executable file is loaded to memory at startup" might be something you were going to do anyway, if you are running a latency-sensitive service. There's nothing worse than having to page in parts of the program after it starts serving.