Review of the profile parsing code suggests that if two threads are parsing the
IOR, one of the threads could potentially skip a profile. Let us imagine this
scenario

- Two threads are parsing the profiles in the IOR. Both the threads get a
pointer to the first profile. Both the threads find that the first profile is
not usable. 

- Now the first thread increments the profile pointer and sets the next pointer
profile. 

- The second thread could do the same thing too (looking at the way the code is
structured). This would make the second thread skip a profile. Worst of all, if
that profile (the third one) is not usable it could return an exception.