Bug 936 – second page of www.washingtonpost.com articles crashes browser

Bug 936 - second page of www.washingtonpost.com articles crashes browser


Summary:	second page of www.washingtonpost.com articles crashes browser

Status:	RESOLVED WONTFIX

Product:	X-Discontinued
Component:	Browser Opera engine (770/N800)
Version:	2.1
Platform:	770 Maemo

Importance:	Medium normal (vote)
Target Milestone:	---
Assigned To:	unassigned
QA Contact:	opera-engine-bugs

URL:	http://www.washingtonpost.com
Keywords:	crash, ITOS2007HE-garage

Depends on:
Blocks:
	Show dependency tree

Reported:	2007-01-07 05:40 UTC by David Talmage
Modified:	2008-12-06 15:41 UTC (History)
CC List:	0 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description David Talmage (reporter) 2007-01-07 05:40:36 UTC

Read any article on www.washingtonpost.com.  Click on the link to the second 
page.  The browser will crash.  If there are more than two pages to the 
article, clicking on the link for any of them will crash the browser.

I'm using version 2.2006.39-14.  It's what came with my 770 when I bought it in 
mid-December 2006.

Comment 1 David Talmage (reporter) 2007-02-04 05:39:32 UTC

The web browser included with version 2.2006.49-2 behaves the same way.

Comment 2 David Talmage (reporter) 2007-05-16 20:03:44 UTC

Hi!  What's happening, Mr. or Ms. Maemo QA?

Comment 3 timeless 2007-10-16 00:02:06 UTC

https://garage.maemo.org/tracker/index.php?func=detail&aid=1347&group_id=164&atid=681

Comment 4 timeless 2007-10-16 20:12:52 UTC

reporter, a few things which help diagnose problems:
1. try disabling plugins
2. try disabling javascript
3. try disabling images
4. create a folder on your mmc named "crash-dumps"
5. try installing microb from http://browser.garage.maemo.org/news/6/
6. try enabling swap (requires an mmc with >64mb of free space) in the Memory
applet in Control panel.
7. instead of clicking an article from washingtonpost.com and then clicking a
link. try:
 a. open browser to http://www.washingtonpost.com
 b. create a bookmark for an article from that page
 c. quit
 d. open the browser from the bookmark
 e. click a link
8. you can try saving the articles and then loading them locally

make notes of which things do and which things don't fix the problem.

FWIW, (the two overworked people who make up) Maemo QA are retiring, and we're
trying to grow users to replace them.

Note that we're not developing Opera, so bugs such as this one get very little
attention.

Comment 5 David Talmage (reporter) 2007-10-17 20:11:17 UTC

(In reply to comment #4)

When I disabled javascript, the browser stopped crashing on washingtonpost.com
articles.  When I enabled javascript, the problem returned.

I did not try any of the other suggestions.

Thanks for all the suggestions.  I'm happy that I can now read any article on
washingtonpost.com

Comment 6 timeless 2008-05-30 13:32:54 UTC

i'm glad that worked for you.

as we're no longer shipping opera this bug will not be fixed.