Well yeah I've done enough, I even exerted more effort that is typically beyond my capabilities to help track down this issue and provide enough "important" information that I thought would be useful to developers.
There's not much more that I can do, it's up to developers to decide whether or not to use this information in order to fix the issue. From what I've observed, there doesn't seem to be much interest on the developer forefront to fix the issue as can be perceived by the lack of comments from other developers both in this thread and on the issue tracker.
Keisel has done a tremendous job with the information and contributions he has provided in this thread. Hopefully he has narrowed this the source of this issue down a bit further than I previously did. I guess there is nothing else to do but sit back and wait and hope this issue will finally get fixed someday.
There's not much more that I can do, it's up to developers to decide whether or not to use this information in order to fix the issue. From what I've observed, there doesn't seem to be much interest on the developer forefront to fix the issue as can be perceived by the lack of comments from other developers both in this thread and on the issue tracker.
Keisel has done a tremendous job with the information and contributions he has provided in this thread. Hopefully he has narrowed this the source of this issue down a bit further than I previously did. I guess there is nothing else to do but sit back and wait and hope this issue will finally get fixed someday.



![[Image: ki2srl-4.png]](http://valid.canardpc.com/cache/banner/ki2srl-4.png)