The issue is in the form for the 1099-B in the webpage or the back-end. If I remove the offending entry, which happens to be the last entry in the list as the list is sorted alphabetically, the error now appears for the entry immediately preceding this one. This makes it clear that the problem is likely in the code which parses the data for the page. Because this seems to follow the last entry in the page, it would seem to be some sort of an issue with the end of file code. This follows too because when I am prompted to fix the issue in the review section and the browser is attempting to render the actual form, this is where the hang occurs, which also seems to support the theory that it is an issue with parsing the data. I have also noted that the code for the tabular display of the data in the page also seems to spike CPU, so seems like there is some sort of a deadlock situation with the code on that page. Note that I too have attempted with three different browsers on two different machines. One more piece of data that might be useful, I began reviewing each entry, out of 388 on my 1099-b, and I noted that in some cases, even though the term (short or long) was entered in the imported dataset, it did not appear for certain entries in the form, which might also support the parsing theory. However, when I went back and reviewed these entries again, the term was defined, so it seems like there is an issue with the parsing of the dataset.
