Ticket #8314 (closed defect: fixed)

Opened 6 years ago

Last modified 20 months ago

Browse crashes when viewing OLPC Community News

Reported by: gnu Owned by: erikos
Priority: blocker Milestone: 8.2.0 (was Update.2)
Component: browse-activity Version: not specified
Keywords: Cc: dsd, dsaxena, gregorio
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description

8.2-759, with Q2E15.

Start Browse. Click on "see the release notes" on the homepage. (You'll need a net connection.) When you get them, click on "Community News" in the left margin.

If I sit there for a couple of minutes, the mouse gets very laggy. Then Browse crashes and pops me back to either the Network page or the Journal.

Pretty simple. Two clicks away from the built-in homepage. I don't see a kernel OOM in dmesg.

Change History

Changed 6 years ago by dsd

  • cc dsd added

Changed 6 years ago by gregorio

  • cc dsaxena, gregorio added
  • priority changed from normal to blocker
  • milestone changed from Not Triaged to 8.2.0 (was Update.2)

Hi Guys,

This is a serious problem.

Do we know if browse crashes more often than before (e.g. earlier joyride or 70x)?

Erikos,

Please make this a top priority to at least understand and scope what can be done to prevent crashes on basic web surfing.

See also 8316 and 8317.

I'm not setting blocker right now but if its a regression I think we should consider that.

Thanks,

Greg S

Changed 6 years ago by dsaxena

Reproduced this with an OOM:

[33901.080562] Free swap:            0kB
[33901.094699] 60416 pages of RAM
[33901.094699] 0 pages of HIGHMEM
[33901.094780] 1477 reserved pages
[33901.097937] 2160 pages shared
[33901.100918] 0 pages swap cached
[33901.104800] 0 pages dirty
[33901.107433] 0 pages writeback
[33901.110416] 5 pages mapped
[33901.114763] 5239 pages slab
[33901.117571] 287 pages pagetables
[33901.120816] Out of memory: kill process 1164 (python) score 54426 or a child
[33901.124833] Killed process 1164 (python)

Ran browse again and reproduced the crash but no OOM killer message this time.

Changed 6 years ago by dsaxena

Rebooted the system and ran browse. This time I got something more similar to #8316 where browse did not crash but my whole systeme appeared completely dead. I was running top in the console and that stopped responding and it looked like the GUI was dead too; however, I could still ping the machine. The system was still running, just very very slowly. Touching the trackpad or pressing the enter key in the console shell works, but there is a huge lag. Clearly, we're massively thrashing here when we should just OOM.

There are two issues here:

1) Kernel is not OOMing when it should, causing overall system degradation (#8316)

2) Browse needs to better handle large pages/images so it does not chew up all system memory in the first place (this bug).

Changed 6 years ago by thomaswamm

See also #8719 (OLPC Wiki Community news crashes Firefox-6 and Browse-98)(in 8.2-765)

and http://wiki.laptop.org/go/Toxic_wiki_pages

I dared to fix the Community News wiki page (there were a few excessively large image files), but someday someone is going to break it again. It would be much better to make Browse and Firefox immune to toxic web pages.

There are other tickets reporting toxic web pages, for example #8003.

Changed 20 months ago by godiard

  • status changed from new to closed
  • resolution set to fixed

This, and all the pages in http://wiki.laptop.org/go/Toxic_wiki_pages work ok with Browse 140

Note: See TracTickets for help on using tickets.