[Cuis-dev] VectorGrahicsPlugin Troubles (WAS: Re: A few tweaks to preferences)

Gerald Klix cuis.01 at klix.ch
Sat Aug 21 10:24:29 PDT 2021


Alas I had another SegFault, that happened after a 2h pause
after testing your changes, I wanted to change the screen size
in Haver (with no background image).

I attached the crash.dmp-file. It is probably not that helpful,
I stripped the VM and its plugins.


HTH,

Gerald



On 8/21/21 7:18 PM, Juan Vuletich via Cuis-dev wrote:
> On 8/20/2021 11:56 PM, Phil B via Cuis-dev wrote:
>> Juan,
>>
>> On Fri, Aug 20, 2021 at 10:34 PM Juan Vuletich via Cuis-dev 
>> <cuis-dev at lists.cuis.st <mailto:cuis-dev at lists.cuis.st>> wrote:
>>
>>     Thanks Gerald. I have experienced occasional crashes when zooming
>>     heavy
>>     windows, but this surely makes it more likely to happen. I can't
>>     test it
>>     right now (I need Windows or Linux), but I thought of a possible
>>     reason
>>     for the problem. If many drag-the-scale-handle events are
>>     processed in
>>     the same Morphic cycle, and processing each takes too much time, next
>>     cycle will take longer, so it will process even more of those
>>     events (if
>>     generated at a constant rate by an insisting user). The growth is
>>     exponential, with no bound. So this is guaranteed to end badly!
>>
>>
>> Yes, this can be an issue with non-VG Morphic too if one isn't 
>> careful.  I've run into it with everything from scrolling to mouse 
>> moves to dragging etc.  VG likely just makes it a more frequent issue 
>> given the overhead of the increased drawing time per frame.
>>
>>
>>     I just pushed an update that limits the processing of
>>     MouseMoveEvents to
>>     just one per cycle. The other kinds of events are much less likely to
>>     cause this kind of problems (although not completely impossible), and
>>     are (as usual) processed until the event queue is empty.
>>
>>
>> Please don't discard events like this.  It will have an impact on 
>> sensitivity/resolution which is already not great.  Can we do some 
>> combination of coalescing and/or more selectively discarding them 
>> instead?
> 
> The point is to improve sensitivity to user actions. Slowing down the 
> Morphic cycle, reducing fps, to process events that won't give feedback 
> to the user until the next cycle is what makes it worse. The way to 
> improve is to give the user feedback as quickly as possible.
> 
>>
>>
>>     Please try again with this updates if you have the chance. It may
>>     help.
>>
>>     Thanks,
>>
>>     --     Juan Vuletich
>>     www.cuis-smalltalk.org <http://www.cuis-smalltalk.org>
>>     https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev
>>     https://github.com/jvuletich
>>     https://www.linkedin.com/in/juan-vuletich-75611b3
>>     @JuanVuletich
>>
>>
>> Thanks,
>> Phil
> 
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: crash.dmp
Type: application/vnd.tcpdump.pcap
Size: 31766 bytes
Desc: not available
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20210821/2f114735/attachment-0001.cap>


More information about the Cuis-dev mailing list