Hi Malu,
I think you can ignore my previous comment about delay in
Debug view, I don't think it's your problem. If I
understood you correctly then most likely you are creating
the delay in the display executor by calling the target on
this thread. Any blocking call in the display thread will
freeze the UI. But honestly, I don't think I can give you
any useful advice without knowing a lot more about your
custom view and your target. I suggest you try to turn on
as much tracing as you can try to debug your timing problem
that way.
Cheers,
Pawel
On 09/24/2012 11:33 PM, Malu Sasi wrote:
Dear Pawel,
Yes of course
I see some delay when the custom view is opened, because
if the view is closed, debug view gets updated within no
time…
For filling
each row of custom view some commands are send to target,
and after processing it is displayed in view. Of course
this processing may take some time, but as said in
previous mail, these operation are written to be
dispatched in Display. getdefault().asyncExec() thread. So this should be running
in a separate thread, that will not affect others.
Also one thing I missed to mention ,
the executor used in DataRequestMonitor for dispatching
commands to target is - DisplayDsfExecutor.getDisplayDsfExecutor(fViewer.getTable().getDisplay());
Can I suspect this executor for this
delay?
Also I have one more doubt in your
reply : “This is done
to allow other views to update first. “
Does this means that the debug view
will always wait for other views to get updated?
If so is it that we can’t change this behavior?
Please guide me on the right way…
Thanks,
Malu
Hi Malu,
There is an intentional delay added (200ms) in updating
the stack trace (except for the top stack frame). This is
done to allow other views to update first. Do
you see other delays?
Cheers,
Pawel
On 09/20/2012 11:11 PM, Malu Sasi wrote:
Hi All,
I am implementing a view using
ILazyContentProvider ; It works well but a performance
lag is noticed in updating debug view.
That is if the view is opened and if a
debug operation is done (Run and halt the target),the
Debug view gets updated only after the visible items in my
custom view is updated.
Custom view is updated using
Display.getdefault().asyncExec() … thread after catching
the suspended event from handleDSFEvents().
Is this an issue related to the Display
thread which I use?
Can anyone please direct me on why the
debug view is waiting for the custom view to get updated?
Thanks in Advance,
Malu
*****
Confidentiality Statement/Disclaimer *****
This message and any attachments is intended for the
sole use of the intended recipient. It may contain
confidential information. Any unauthorized use,
dissemination or modification is strictly prohibited. If
you are not the intended recipient, please notify the
sender immediately then delete it from all your systems,
and do not copy, use or print. Internet communications
are not secure and it is the responsibility of the
recipient to make sure that it is virus/malicious code
exempt.
The company/sender cannot be responsible for any
unauthorized alterations or modifications made to the
contents. If you require any form of confirmation of the
contents, please contact the company/sender. The
company/sender is not liable for any errors or omissions
in the content of this message.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
***** Confidentiality
Statement/Disclaimer *****
This message and any attachments is intended for the sole
use of the intended recipient. It may contain confidential
information. Any unauthorized use, dissemination or
modification is strictly prohibited. If you are not the
intended recipient, please notify the sender immediately
then delete it from all your systems, and do not copy, use
or print. Internet communications are not secure and it is
the responsibility of the recipient to make sure that it
is virus/malicious code exempt.
The company/sender cannot be responsible for any
unauthorized alterations or modifications made to the
contents. If you require any form of confirmation of the
contents, please contact the company/sender. The
company/sender is not liable for any errors or omissions
in the content of this message.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev