Closed dbeniamine closed 8 years ago
I did not test the trace you provided but that sounds like the overview is still in computation. The overview is launched as a background thread once the main computation is done, but with the number of event producers you have it must consume too much resources.
You can disable it in the Ocelotl options : Overview tab -> uncheck Display Overview.
It seems indeed to solve the problem, thanks :)
Hi,
I'm still working on new Moca traces (I've just updated the importer on the inria gforge), when I try to visualize these traces with Ocelotl, it generate some java processes that keep using (almost) 100% of all my CPUs when Ocelotl has finished to compute the visualization and make Framesoc unresponsive. Furthermore if I quit both Framesoc (by killing it) and eclipse (properly) I still have these 4 processes up an running ...
Here what I can see of them with a
ps
:Any idea ?
P.S: My traces have 47152 event producers for 405215 events. P.P.S: There are the trace files: newMoca.zip
David