I think i figured it out, it is a quite individual mistake though.
The error occurred in some cases when calling the reloadSections:withRowAnimation:
Method on the concerned UITableView
Object. Using reloadData
solved the issue.
The mistake itself is difficult to explain, since this would mean to explain a big part of the concerned apps implementation. Anyway I think that it is caused by performing a lot of consequent reloadSections:withRowAnimation:
mixed up with reloadData
Method calls in a short time period. My app has several asynchronous calls to the reloadSections:withRowAnimation:
method when new data is received through a UDP-Socket, and when in the meantime the user performs a tableview reload manually (when using a filter on the tableview - the buttons at the bottom of the view are used for that) this might actually cause a problem.
I think some already created Sectionheader-views objects might not get cleaned up so that they remain stuck to the superview. I'm not sure whether it is the right explanation, but the problem is fixed at least :)