Hi (again) Phil:
Two further thoughts.
* All those preprocessing directives and fprintf calls I inserted make
it extremely hard to understand the code. Thus, feel free to revert
my two commits completely that inserted the debug output in
PLMemoryMap:create and PLMemoryMap:close when you finally
On 2016-12-10 13:21-0800 Alan W. Irwin wrote:
[...]
> So instead of pursuing this with inserting timing statements like you
> are thinking about, instead I plan to simply insert more debug prints,
> e.g., "PLMemoryMap::create: entering", PLMemoryMap::create: calling
> close" in the
On 2016-12-10 13:41- p.d.rosenb...@gmail.com wrote:
> Many thanks Alan for pushing this and getting the debug statements into the
> code. You have confirmed that i was looking in the wrong place for the
> problem.
>
> I was mulling things over this morning and wondered about the same thing
Many thanks Alan for pushing this and getting the debug statements into the
code. You have confirmed that i was looking in the wrong place for the problem.
I was mulling things over this morning and wondered about the same thing as
you, some sort of memory leak with the shared memory. You have
Hi Phil:
If you review my results from much earlier this year that had a screen
shot attached in the next e-mail of my cpumeter results, the test
being run was for a case with absolutely no text data being written to
wxPLViewer. So your concern (expressed off list to me) about the
efficiency of
