Mail Archives: geda-help/2020/11/15/13:51:31
Roland,
Thanks for answering my email.
> On Nov 15, 2020, at 2:26 AM, Roland Lutz <rlutz AT hedmen DOT org> wrote:
>
> On Sat, 14 Nov 2020, Roger Traylor (traylor AT engr DOT orst DOT edu) [via geda-help AT delorie DOT com] wrote:
>> Was using gschem yesterday for hours without issue. Went for a break and when I came back, I resized the docked window on the right that allows for edits of text, libraries, attributes, etc.
>
> So the error only started to appear after you resized the dock?
I always try to remember the very last thing that changed when I see a new error in hardware
or software appear. Resizing the dock was the last thing. It may or may not be relevant but
odd behaviors occurred directly after resizing.
> This may be an issue with a missing (or too low) minimum size of one of the UI elements. I have spent some time making the docks work even when resized to a very small size, but I may have missed something.
The resizing was relatively minor. I moved the left edge to the right a little bit to see more of
my schematic. Maybe shrinking the dock size by 20%. It was still sizable.
> Have you tried increasing the size of the dock again?
When I invoke the tool now, I cannot grab the left edge the dock to change its size.
If I resize the entire window, say bigger, the window grows, but the dock is not “repainted” for about 15 seconds.
If I shrink the window, the dock shrinks.
If I minimize the window and then maximize again, only the very bottom of the gschem window (pick, pan….)
is repainted until about 15 seconds passes at which time the full window reappears.
All commands take a long time to execute. For example “view extents” takes 5-6 seconds.
Menu items are non-functional.
> It would be helpful to know *which* window is causing the problem, i.e., which which set of windows in the right dock the problem is reproducible.
Not sure what you are asking. But the tabs “Library, Object,Text, Attributes” have a very long delay once clicked
(>1 minute) and choosing any of them seems to make no difference in behavior I’m seeing.
>> A correct schematic will appear on the editing screen, but application response is very slow.
>> “top” indicates that gschem is using 98% of CPU.
>
> Hmm… That may be a GTK problem, or it may not. Would it trouble you to start gschem in a debugger and find out where this time is spent?
I’d certainly be happy to try to get to the bottom of this. I’m not much of a SW developer type but have good
basic linux skills. Let me know what to do and I’ll try it.
I’m wondering if gschem has cached some data about the present UI parameters that a reinstall would not touch.
Just an uninformed guess. Can’t seem to find any dot files that would hold this data, but they could be hiding
somewhere I haven’t looked in.
Thanks so much,
Roger
> Roland
- Raw text -