| Summary: | On some pages Konqueror very like crashes | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Slávek Banko <slavek.banko> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | bugwatch, darrella, slavek.banko |
| Priority: | P5 | ||
| Version: | 3.5.13 [Trinity] | ||
| Hardware: | All | ||
| OS: | All | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Attachments: | Backtrace | ||
|
Description
Slávek Banko
2012-06-20 12:15:42 CDT
I just ran a quick test in Trinity. No crash. I run my browsers with just about everything disabled --- therefore we probably should look at which settings are causing the crash. I enabled Javascript and could not get a crash. I did not try enabling Java or cookies. I don't use ad blocking inside my browsers because I block ads on a system-wide basis. I do not have flash enabled in konqueror. Interesting. I have JavaScript and cookies enabled. Flash I do not like - I have not installed. The backtrace (I have several of them) you can see, it always falls in htmltokenizer.cpp. I need to simulate your konqueror settings to create a like-for-like test with respect to konqueror. Other things might still influence the problem such as video drivers. (Odpověď na komentář #3)
> I need to simulate your konqueror settings to create a like-for-like test with
> respect to konqueror. Other things might still influence the problem such as
> video drivers.
Video driver can be excluded - crashes on different machines with different graphics cards (ATI, Matrox, Intel, nVidia). Track leading to htmltokenizer suggests that it probably will not be a hardware problem.
Adding a note that this report might be related to bug report 249. (Odpověď na komentář #5) > Adding a note that this report might be related to bug report 249. Very good point. This is probably the identical error. Therefore, I mark this newer bug report as a duplicate... *** This bug has been marked as a duplicate of bug 249 *** |