I have an lwip application and two development setups. Using the same source code and project files, one setup runs as expected while the other fails. I've noticed that on the one that fails, the Statistical Profiling window shows that the VDK_ISRAddHistoryEvent consumes most of the processing time immediately after the application run. On the setup that run successfully, the VDK_ISRAddHistoryEvent barely shows up on the Statistical Profiling window. What can cause the VDK_ISRAddHistoryEvent to run wild on the setup that failed?