A decompression bomb just means that the file is highly compressed so Avast will not open it during a scan however, if it is opened by another programme it will be monitored
The clientmonitor saves all data into a temptable. A temptable is first kept in memory, but if it gets to big, it is saved on the local disk.
Because of historical reasons, a file created or opened by Navision CANNOT supperate 2GB. If it superates these 2GB, you get that error.
To solve it, you might try to let the client monitor take less data (untoggle some things you don’t need) or try to let your report calculate less data.
Error message when you run a report or a dataport in Microsoft Dynamics NAV 4.0 or in Microsoft Business Solutions - Navision 3.7: "Operating System Returned the Error (131). An attempt was made to move the file pointer before the beginning of the…
If I may add to essexboy’s remarks … a so-called decompression bomb is (or at least used to be) typically compressed in several sequential stages, each stage using a different compression method to allow further compression. Therefore the end result could be as much as several orders of magnitude smaller than the original file, as compared with, e.g., a common self-extracting exe, which might be a few dozen times smaller than its contents.
While we haven’t seen much news about such “bombs” lately, we used to get lots of complaints about the worst-case scenario when trying to re-expand one, where in some cases the user would run out of disk space with one or more stages of decompression still to go.