I'm not totally sure, but it could be the one feature failing for different reasons. The IssueLocations port is probably highlighting where the problems occur (like that feature failed with a problem in 265 locations). The invalid parts is similar, highlighting which parts of the feature are bad. If it's an aggregate feature (composed of multiple geometric elements) that might also explain why there are multiple outputs. In short, I think you'd need to visually inspect the output to see what it is composed of.

Many thanks @mark2atsafe​ . The feature I'm trying to read is an aggregated feature indeed. My problem is weather it is deaggregated or not, the feature is clean prior to writing (image 1), while the simple fact of writing and reading it (ESRI feature class in file geodatabase) makes all these problems appear whether I'm reading the feature as aggregated or deaggregated (image 2). Would you have any idea on how writing the feature could generate errors?



"Would you have any idea on how writing the feature could generate errors?"

Because it's ESRI :-)

The coordinates that are written in the geometry in the feature class will not necessarily exactly match the coordinates that exist in the feature prior to writing, it is influenced by the XY tolerance and resolution settings