This forum has been archived. All content is frozen. Please use KDE Discuss instead.

konqueror crash upon login on google, yahoo...

Tags: None
(comma "," separated)
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Ok, I would suggest asking on the Konqueror development mailing list, kfm-devel@kde.org, at this stage of the process. Please include all the information I listed in the previous post in your email to the list.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
papapenguin
Registered Member
Posts
45
Karma
0
OS
ok, so it's definitely chat that locks up konqueror...

...I don't have new fault threads as when chat loads, konqueror completely freezes but does not fail, therefore does not create a fault...I've left it 'open' overnight to see if something is just taking time to load, but to no avail...

...as I said before, the mouse works, and I can click anything in the task manager toolbar to switch to another open application, but konqueror is completely frozen...

To test this, I went to my Windows 7 machine (yes, to fix something in KDE, I resorted to Windows, how sad), disabled chat in google, came back to my KDE machine and found no problems...everything seems to work fine...

...now if only I could use chat in google...
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Have you sent the information in question to the kfm-devel@kde.org mailing list?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
papapenguin
Registered Member
Posts
45
Karma
0
OS
I have not, but I have filed a bug report...it seems that it is a duplicate of another bug, but not necessarily in chat...

Do you think I should just write a short explanation and include the link to this thread?
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
I don't think it'll be needed in this case.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
GTalbot
Registered Member
Posts
69
Karma
1
OS
papapenguin wrote:is there any way I can monitor the code or the processes that happen during this lock-up/freeze in Konqueror?


To monitor (step into) the code, activate the javascript debugger:

Configuration/Configure Konqueror/Internet Navigation section/Java & Javascript category/Activate debugger

I think the JS debugger activates only on errors, not on hang processes.

papapenguin wrote:Right now I'm not able to create a crash, only a total freeze and 100% spike in computer usage...


I know of hang bugs in Konqueror. I have filed them:

Generated content (:before and :after) and display table- types create a maximized CPU % activity and a hang bug (infinite reflow).

Bug #247033

Bug 247033 - [testcase] Generated content and display table- types hangs Konqueror 4.4.5


papapenguin wrote:then I must click a number of times on the exit button before I get a window that tells me 'Konqueror is not responding do you with to terminate?'...

I would like to file a bug, as well...


Yes. This is a hang application bug: in my opinion, these kinds of bugs are more serious than application crash bug. Because with crash, the user knows there is something wrong and (s)he may chose not to revisit the page... while hang bug may not be noticed by the user and it will affect his/her surfing.

Gérard


GTalbot
Registered Member
Posts
69
Karma
1
OS
papapenguin wrote:(...) I have filed a bug report...it seems that it is a duplicate of another bug, but not necessarily in chat...


papapenguin, what was that bug report number please?

papapenguin wrote:Do you think I should just write a short explanation and include the link to this thread?


Yes, it could help. At this point, what is best is to do is to create a reduced testcase reproducing the hang application.

Investigating Konqueror Bugs says

Unfortunately due to the large number of bug reports received, and the large amount of time that it takes developers to identify issues, reports which do not include a testcase or are not described in reproduceable steps will get a low priority of fixing.

(...)

5. The important part is: the page should be as short as possible to be able to still reproduce the bug. The shorter it is, the sooner it will get fixed!


regards, Gérard




Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]