We spent some time last week trying to troublshoot an issue where one user was unable to use a Flex application we developed. It was quite maddeing actaully, I was able to use the application from 4 different computers in my house using 4 different browser versions (IE 6, IE 7, FF 2 and Safari for Windows). Other people at Alagad were also able to use the application as well. The user who was unable to use the application was even able to use it when he tried from different computers in his office, but not from his normal workstation.
The culprit, as was discovered, was ColdFusion debugging. For some reason, ColdFusion debugging was interfering with one, not all, just one of the remoting calls. The odd thing is that after being alerted to this, I enabled ColdFusion debugging and I was able to use that application without issue. The user who was having problems was able to use the application after turning off debugging, and it continued to work after debugging was turned on again.
I used to keep debugging turned on all the time on my development machine, but, when I staretd doing a fair amount of Model-Glue, and other framework, development, the page load times were sometimes unbearably long and turning off debugging reduced those times drastically. Now, I only turn on debugging when I need it, and even then, its mostly to view queries that were run (or should have been run).
So, this got me thinking, is what I am doing more the norm or do most people keep dubuging enabled all the time in development?