Obfuscated code causes an out of memory exception
ianb
Posts: 1 New member
Hi all,
Using Redgate's smartassemby obfuscator, we found that the obfuscated build crashed with an out of memory exception when running the product with 4 or 5 X's. But with an unobfuscated build, the system could get to 20+ X's. Has anyone else seen this type of problem, or have any ideas what the problem could be?
We have identified the individual assembly that causes the problem when obfuscated, but there is currently no clue as to why and hence how we can resolve the problem (without stopping using the tool and not obfuscating, or trying a new tool)
Using Redgate's smartassemby obfuscator, we found that the obfuscated build crashed with an out of memory exception when running the product with 4 or 5 X's. But with an unobfuscated build, the system could get to 20+ X's. Has anyone else seen this type of problem, or have any ideas what the problem could be?
We have identified the individual assembly that causes the problem when obfuscated, but there is currently no clue as to why and hence how we can resolve the problem (without stopping using the tool and not obfuscating, or trying a new tool)
