normally, this happens when you are trying to show too many values on your table or when computing the table takes too much memory, depending on the RAM that is available on your computer / server.
This is not intuitively linked to the changes you are making to the table. If you keep it this way, the risk is that the message will appear "randomly" when the load is too high, looking like it's a bug.
Reloading, re-opening the app and stuff like this will just be a temporary fix but will not solve the root of the problem.
You have to try to reduce the amount of data you want to include in the table (think about the user experience) or use a machine with more RAM if you cannot shrink it further.
I recently have seen Out of Object memory issue in one of our QVWs while using a pivot table with full expansion mode.
I was surprised to see that with just 120K records and the QVW file size of 14 MB was taking a RAM size of 20 GB.
We resolved this issue by using simplified version of the expressions.I had nested if else in my expression. I changed them all to conditional display and used set analysis.
So my suggestions is:
1. Open the QVW in your local and open the task manager and test how much memory the Qv.exe process is taking
2. If you have used any if else logic then try to avoid it and use simple expression. Better to use set analysis wherever possible.
If you can also attach the scrambled copy of the qvw then I could test this in my system.
I certainly agree with Brice on the above he just mentioned.
Reloading is a temporary fix,its not something that will permanently solve your problem.
You can try something like this:
Try and adjust the transparency as per you choice,if its green that you want.
pivot.png 309.7 K