|Re: [dsdp-dd-dev] DsfMemoryBlock deadlock on memory write?|
Unfortunately the request flood is still there even after applying the patch to DsfMemoryBlock L
Now the writing to memory issue is fixed both in GDB and our debugger, thanks.
Wouldn't it be better to have the query.get() calls in DsfMemoryBlock.writeMemoryBlock() and fetchMemoryBlock() fail after a timeout? Or should the timeout happen in the IMemory service implementation, throwing an ExecutionException if needed?
From: dsdp-dd-dev-bounces@xxxxxxxxxxx [mailto:dsdp-dd-dev-bounces@xxxxxxxxxxx] On Behalf Of Mario Pierro
Sent: den 22 januari 2009 09:17Subject: RE: [dsdp-dd-dev] DsfMemoryBlock deadlock on memory write?
To: Device Debugging developer discussions
I am glad that this has been fixed!
There had been a discussion in this mailing list some time ago about our implementation of the IMemory service being flooded with calls when the mouse wheel was used to scroll the Memory View.
The missing done() / thread leak when fetching memory blocks could have been the cause for the slowdown we had…
I'll try that again with the patched version of DsfMemoryBlock to check if there are any improvements.
Back to the top