id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
2778	OMEdit often can't parse xml output	Adam Dershowitz <dersh@…>	Adeel Asghar	"Very often, when I run a simulation in OMEdit, on my Mac, it works fine.  But, it seems that the output results don't get parsed properly.  Everything else works, and I can see the actual data.  It is just the output log stats.  So, what I see in the Output window looks like this:

{{{
/private/var/folders/s4/0j3cshj161126ygbpbzsdkmd4h24dl/T/OpenModelica_adershowitz/OMEdit/Modelica.Mechanics.MultiBody.Examples.Elementary.DoublePendulum -port=63007 -logFormat=xml -w -lv=LOG_STATS
Error while parsing message xml tag mismatch 15:7
<message stream=""LOG_STATS"" type=""info"" text=""### STATISTICS ###"" />
<message stream=""LOG_STATS"" type=""info"" text=""timer"">
<message stream=""LOG_STATS"" type=""info"" text=""    0.045562s          reading init.xml"" />
<message stream=""LOG_STATS"" type=""info"" text=""   0.0506857s          reading info.xml"" />
<message stream=""LOG_STATS"" type=""info"" text=""  0.00264133s          pre-initialization"" />
<message stream=""LOG_STATS"" type=""info"" text=""  0.00040838s [  2.4%] initialization"" />
<message stream=""LOG_STATS"" type=""info"" text=""   1.277e-05s [  0.1%] steps"" />
<message stream=""LOG_STATS"" type=""info"" text=""  0.00785925s [ 46.4%] creating output-file"" />
<message stream=""LOG_STATS"" type=""info"" text=""  4.4513e-05s [  0.3%] event-handling"" />
<message stream=""LOG_STATS"" type=""info"" text="" 0.000625647s [  3.7%] overhead"" />
<message stream=""LOG_STATS"" type=""info"" text=""  0.00535942s [ 31.6%] simulation"" />
<message stream=""LOG_STATS"" type=""info"" text=""   0.0169513s [100.0%] total"" />
</message>
<message stream=""LOG_STATS"" type=""info"" text=""events"">
Error while parsing message xml tag mismatch 3:10
<message stream=""LOG_STATS"" type=""info"" text=""    0 state events"" />
<message stream=""LOG_STATS"" type=""info"" text=""    0 time events"" />
</message>
<message stream=""LOG_STATS"" type=""info"" text=""solver: DASSL"">
<message stream=""LOG_STATS"" type=""info"" text=""  350 steps taken"" />
<message stream=""LOG_STATS"" type=""info"" text=""  535 calls of functionODE"" />
<message stream=""LOG_STATS"" type=""info"" text=""   37 evaluations of jacobian"" />
<message stream=""LOG_STATS"" type=""info"" text=""   21 error test failures"" />
<message stream=""LOG_STATS"" type=""info"" text=""    0 convergence test failures"" />
</message>
<message stream=""LOG_STATS"" type=""info"" text=""### END STATISTICS ###"" />

}}}
I would estimate that this happens about half the time.  And, I have not yet figured out when it does or doesn't happen.  It just seems somewhat random.  But, to be clear, even when it happens the actual results are fine, it is just the displayed stats that end up showing all of the XML markup, and the error that it can't be parsed.  
Note that everything starting with Error is red, so it clearly shows as an error.
"	defect	closed	high	1.9.2	OMEdit	trunk	fixed