bugGNU Octave - Bugs: bug #65477, Using character '^' starts a 100%...

 
 

bug #65477: Using character '^' starts a 100% cpu process in gnome wayland

Submitter:  None
Submitted:  Sun 17 Mar 2024 09:36:55 PM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Performance
Status:  None Assigned to:  None
Originator Name:  Julio Gardona Originator Email:  -email is unavailable-
Open/Closed:  * Open Release:  * stable
Operating System:  * GNU/Linux Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Mon 29 Jul 2024 10:04:20 AM UTC, comment #14: 

Hi, maye I've found a way to reproduce it: use a special keyboard like the (US alt. intl.) and just insert a special key like ^,",',`,...

With the special keyboard, these keys may be used as a normal key (KEY double press or KEY + SPACE BAR) or as a modifier of the next character to have some special accented character (i.e. è, é, ë, ê).

After the first special key is pressed, Octave go crazy to 100% of CPU usage. Problem is graphical, as if you resize or move in background Octave it stops until you reopen Octave windows.

Problem seen on:
Fedora: 39, 40
Wayland and Xorg
octave 8.4, 9.1, 9.2 (dnf repo, flathub, from source)

Hoping this may be useful to solve.

Thanks
Ciao


Anonymous
Tue 09 Apr 2024 03:16:19 PM UTC, comment #13: 

Unless an Octave developer can reproduce, we don't have a way to debug this issue.  Dmitri does run Fedora and he could not recreate problem.

 Rik <rik5>
Group administrator
Tue 19 Mar 2024 06:27:27 PM UTC, comment #12: 


comentário #11:

> Can anyone explain exactly how I might try to reproduce this problem?  On my system, I see
>


> $ ps axuww | grep -i wayland
> jwe       115361  0.0  0.0 162388  5888 tty2     Ssl+ 14:03   0:00 /usr/libexec/gdm-wayland-session env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --session=ubuntu
> jwe       115876  0.2  0.4 1331644 79160 ?       Sl   14:03   0:00 /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.VCH1K2 -listen 4 -listen 5 -displayfd 6 -initfd 7


Hello, good afternoon. I have already tested on x11 xorg and the issue doesn't happens. It only happens in wayland fedora. In another distros I hadn't tested. I have uploaded a video to my gdrive explaining how to reproduce.


https://drive.google.com/file/d/1q2oUu0_pWGjDlXefE7s_8vgvk4FpO7bF/view?usp=drive_link

>
> Does that mean I am using Wayland in the way that is meant in this report?
>
> I normally run Octave builds across an ssh connection (ssh -X to a remote system, run Octave there and display on the Ubuntu system that is running Xwayland).  But if it might matter, I can try to build a copy of Octave that will run locally on my Ubuntu system.
>
> Also if it matters, the version of Xwayland on my system is
>


> $ Xwayland -version
> The X.Org Foundation Xwayland Version 22.1.1 (12201001)
> X Protocol Version 11, Revision 0


>
> Also, Octave itself doesn't really do anything directly with X/Xorg/Xwayland.  So it seems likely to me that any issues with those components are likely to be either problems with libraries used by Octave (Qt or other libraries) or bugs in Xwayland itself, not bugs in Octave.

 Anonymous
Tue 19 Mar 2024 06:16:13 PM UTC, comment #11: 

Can anyone explain exactly how I might try to reproduce this problem?  On my system, I see


$ ps axuww | grep -i wayland
jwe       115361  0.0  0.0 162388  5888 tty2     Ssl+ 14:03   0:00 /usr/libexec/gdm-wayland-session env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --session=ubuntu
jwe       115876  0.2  0.4 1331644 79160 ?       Sl   14:03   0:00 /usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mutter-Xwaylandauth.VCH1K2 -listen 4 -listen 5 -displayfd 6 -initfd 7


Does that mean I am using Wayland in the way that is meant in this report?

I normally run Octave builds across an ssh connection (ssh -X to a remote system, run Octave there and display on the Ubuntu system that is running Xwayland).  But if it might matter, I can try to build a copy of Octave that will run locally on my Ubuntu system.

Also if it matters, the version of Xwayland on my system is


$ Xwayland -version
The X.Org Foundation Xwayland Version 22.1.1 (12201001)
X Protocol Version 11, Revision 0


Also, Octave itself doesn't really do anything directly with X/Xorg/Xwayland.  So it seems likely to me that any issues with those components are likely to be either problems with libraries used by Octave (Qt or other libraries) or bugs in Xwayland itself, not bugs in Octave.

 John W. Eaton <jwe>
Group administrator
Mon 18 Mar 2024 01:16:04 AM UTC, comment #10: 

Cant attach the file. This page says limit 16384 kB, and I have a 5000 kb file but it dont uploaded.

 Anonymous
Mon 18 Mar 2024 01:15:26 AM UTC, comment #9: 

files are size limited.  (not sure what the size is). if you can reduce size or post elsewhere and link here that may work better.

 Nicholas Jankowski <nrjank>
Group Member
Mon 18 Mar 2024 01:11:52 AM UTC, comment #8: 

Its clearly a bug. Screen cast attached.

 Anonymous
Mon 18 Mar 2024 01:01:58 AM UTC, comment #7: 


comentário #6:

> I found Wayland to be too buggy to be usable and normally use Xorg. For this specific problem I re-login to Wayland.
> I cannot reproduce the problem.
>
> Dmitri.
> --
>


If we think this way we will need to use octave forever in obsolete systems. Sorry but I can´t agree, and also, I will record my screen and put a video attached here.

 Anonymous
Mon 18 Mar 2024 12:25:52 AM UTC, comment #6: 

I found Wayland to be too buggy to be usable and normally use Xorg. For this specific problem I re-login to Wayland.
I cannot reproduce the problem.

Dmitri.
--

Dmitri A. Sergatskov <dasergatskov>
Mon 18 Mar 2024 12:19:47 AM UTC, comment #5: 

It leads to lots strange behaviors. For example, when the process begins to spend lots of cpu, if I change de octave's tab from Command Window to another, like documentation or even minimize the window, the process will get back to normal, and, when I maximize or got back no Command Window tab, it starts to consum lots of cpu again.

 Anonymous
Mon 18 Mar 2024 12:11:25 AM UTC, comment #4: 


comentário #3:

> I tested specifically on Wayland.
>
> Dmitri.
> --
>


You need to verify the process. It will start to consumn lots of cpu.

Here is my system specification as attached image.


 Anonymous
Mon 18 Mar 2024 12:06:17 AM UTC, comment #3: 

I tested specifically on Wayland.

Dmitri.
--

Dmitri A. Sergatskov <dasergatskov>
Mon 18 Mar 2024 12:03:36 AM UTC, comment #2: 

comentário #1:

> I cannot reproduce this on Fedora 39 with neither self-compiled octave 9.1 (Qt6) nor with distro-provided 8.4.0 (Qt5) (from "updates-testing"). This is with US keyboard and LANG settings.
>
> Perhaps you are using a non-US keyboard and "^" mapped to some control sequence that Wayland misinterprets?
>
> Dmitri.
> --
>


Im already using a us keyboard: English(US Intl. with dead keys). If you are not on a wayland session, using gnome 45 you will not be able to reproduce.

 Anonymous
Sun 17 Mar 2024 11:13:36 PM UTC, comment #1: 

I cannot reproduce this on Fedora 39 with neither self-compiled octave 9.1 (Qt6) nor with distro-provided 8.4.0 (Qt5) (from "updates-testing"). This is with US keyboard and LANG settings.

Perhaps you are using a non-US keyboard and "^" mapped to some control sequence that Wayland misinterprets?

Dmitri.
--

Dmitri A. Sergatskov <dasergatskov>
Sun 17 Mar 2024 09:36:55 PM UTC, original submission:  

Hello, good afternoon

I'm tracking this issue almost a year or two.
In qt gui, under linux x64, wayland and gnome, the Command Window starts a process that consums 100% cpu of a thead. To trigger this issue, you only need to type the character '^' in Command window. This is very annoying and takes lots of cpu overheating and making the fans work hard.

the versions I tracked this issue was octave 8.4.0, 9.1.0.
kernel version - 6.7.9-200.fc39.x86_64

Tryed installed by flathub and by compiling from the sources.


Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #55858:  system.png added by None (42KiB - image/png)
file #55856:  cpu100process.png added by None (91KiB - image/png - I think we need to enhance fixing qt interface to wayland.)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by nrjank (Posted a comment)
  • -email is unavailable- added by dasergatskov (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)

    •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2024-03-18 None Attached File- Added system.png, #55858
    2024-03-17 None Attached File- Added cpu100process.png, #55856

    Back to the top

    Copyright © 2024 Free Software Foundation, Inc.
    Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
    The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team.
    Page source code

    Powered by Savane 3.14-f13d.
    Corresponding source code