Well, if it helps... although I doubt it.
Curiously, manually invoking the profiler by setting OPENCL_PROFILE=1 and OPENCL_PROFILE_CSV=1 doesn't trigger the problem. The output imports into Compute Visual Profiler without any problem. That's a cute workaround, but it'd be cool to see this fixed.
The whole thing seems rather strange though. Does Compute Visual Profiler do anything beyond invoking the profiler and collecting its output?