>I am sure you will remember what it was. As soon as you "walk" away from thinking about it.
Something else to consider is to use SET COVERAGE TO output.log before you get to that line, and then turn it off after. You may find that it's loading something in an associated database, and it is the index there that is the cause of the issue.
SET COVERAGE TO will allow you to see what lines of code are executed and in what order.
Martina Jindrova has created a supplement to the SET COVERAGE TO output, which is an excellent tool allowing you to examine the recorded output log file, and to export a new LOG file with actual source code on each line, allowing you to see line-by-line in source code form what commands were executed:
It's an excellent tool. I use it regularly. I asked her to add in the export with source code and she did. She also wouldn't accept any money for it because she's not only an amazing developer, but also a giver. I can't say enough nice things about her or her tools.
