Bug 279605 - [hang] Opening javascript debugger hangs the application (CPU %tage activity remains, stays high)
Summary: [hang] Opening javascript debugger hangs the application (CPU %tage activity ...
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: kjs (show other bugs)
Version: 4.7.0
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-07 19:10 UTC by Gérard Talbot (no longer involved)
Modified: 2023-01-14 05:12 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gérard Talbot (no longer involved) 2011-08-07 19:10:16 UTC
Version:           4.7.0 (using KDE 4.7.0) 
OS:                Linux

Investigating a javascript reported error with Konqueror JS debugger can create a hung application: CPU %tage activity becomes high and remains high during seconds, minutes (suggesting an infinite loop) until the user "kills" the process.

This bug should be considered+treated higher than normal since without a working and available javascript debugger, we can not identify, investigate javascript bugs and errors.

Just a hunch: this problem may be caused by script functions having no or little white spaces separating functions or javascript code.

Reproducible: Always

Steps to Reproduce:
1- You should have a system surveillance or system monitoring application opened and visible to view the CPU %tage activity of active processes.

2- Configuration/Configure Konqueror.../category Java & Javascript/Javascript tab/Debugging section/Enable debugger and Report errors checkboxes must be checked

3- Visit 
Web browsers (Global marketshare)
http://www.getclicky.com/marketshare/global/web-browsers/

4- The debugger will spawn 2 Javascript Error alert modal windows (with title "Javascript Error") which are respectively saying exactly (albeit translated from French) the following:

[1st error report window]
"
A problem occured when trying to start a script in the page.

http://static.getclicky.com/inc/min/stuff7.js line 5 :
[object DOMException]
"

[2nd error report window]
"
A problem occured when trying to start a script in the page.

http://static.getclicky.com/inc/min/stuff7.js line 275 :
TypeError: Attempt to use a non-function object or a value as a function.
"

5- Click the Debug button of one of the 2 Javascript Error windows

Actual Results:  
a) The javascript debugger window opens but the painting, drawing of its components (menu, toolbar, panels, inside content) is incomplete, is stopped and seems locked. The javascript function data involving the errors never gets displayed.

b) The %tage of CPU activity for the Konqueror application gets high (over 50%) and remains high during well over 30 seconds.

Expected Results:  
a) The javascript debugger window opens with all of its components (menu, toolbar, panels, inside content) fully drawn. The javascript function data involving the errors gets displayed.

b) The %tage of CPU activity for the Konqueror application gets high (over 50%) for no more than 10 seconds and then goes down to normal CPU activity (idle or less than 5%).

I have searched for duplicates. 

I believe the correct component for this bug is kjs but I could be wrong.

KDE Platform Version: 4.7.0
Konqueror version: 4.7.0 (KHTML rendering engine)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-10-generic-pae i686 (32bits)
Distribution: Kubuntu 11.04
here.

regards, Gérard
Comment 1 Gérard Talbot (no longer involved) 2011-08-07 19:19:08 UTC
Erratum and addendum:

Step 5 should be rather
-----------------------
5- Click the Debug button of the 2nd of the 2 Javascript Error windows. Click the Debug button of the Javascript Error window about line 275.


If you "OK" the Javascript Error window about line 275 and then click the Debug button of the 1st Javascript Error window about line 5, then the JS debugger appears with all of its panels and stuff7.js functions are loaded and are displayed.

Gérard
Comment 2 Andrew Crouthamel 2018-11-06 15:05:12 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-17 04:56:59 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2022-12-15 05:49:07 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-12-30 05:23:32 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-01-14 05:12:37 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!