Edge crashes on sites with lots of Ads

Not reproducible Issue #8626269

Details

Author
Derek L.
Created
Aug 24, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14393
Reports
Reported by 5 people

Sign in to watch or report this issue.

Steps to reproduce

Most of the links coming off of MSN.com that lead to top ten lists and other such sites contain javascript to deliver ads to the landing page. Edge routinely fails and causes these pages to need to recover. If you move or touch the browser before the last bit of javascript ad is on the page, the entire browser crashes. Subsequent reloads of the page seem to work properly for a few minutes before the browser crashes again. The behavior doesn’t leave any trail of evidence in the Event Log for Windows either so there is no way to give more information.

Attachments

0 attachments

    Comments and activity

    • This issue only happens with the Anniversary update. Prior to the update, sites would load properly. My machine was a complete formatted hard drive using the Windows Enterprise version found on MSDN that included the update. No extensions have been added to my installation of Edge so far.

    • I’ve been seeing the same thing. Things went south around the middle of the insider program between 1511 and 1608 and never really got better. Seemed to happen around the same time they announced their JavaScript engine is way faster than everyone else’s… well that may be true in a couple benchmarks… but in the real world, it chokes and dies when loading lots of iframes (typically how ads are served) or when scrolling before the page finishes loading ads, or when unloading a page that has lots of iframes (typically ads). It’s practically unusable right now.

    • Microsoft Edge Team

      Changed Status to “Not reproducible”

    • Thank
      you for reporting this issue. We have attempted to reproduce this issue on a
      number of MS Edge builds and we can’t reproduce
      the issue you described. It is always possible we are missing a step in the
      repro. Would it be possible for you to provide us with more details in order to make the browser crash?

      I tried several times with many different articles on msn.com with no crashes.

    • Happens all the time for me. I just opened 3 tabs and browsed to some pages on them:

      1. wonderhowto.com and click through to an article
      2. anandtech.com and click through to an article then go back to the homepage
      3. msn.com still hasn’t finished loading

      Anandtech.com (which currently has a skin ad for LG running) crashed. Proof: http://i.imgur.com/ShY8INm.png

    • (forgot to mention I resized the browser window somewhere along the lines… don’t think that’s the cause though as it literally happens all the time during regular every day muti-tab browsing… honestly can’t believe you can’t reproduce this)

    • Here’s another ad heavy site that Edge chokes on: http://www.androidheadlines.com

    • Perhaps this will help. My event log is loaded with the following two errors:
      Activation of the app Microsoft.MSKAPP_8wekyb3d8bbwe!App for the Windows.BackgroundTasks contract failed with error: The app didn’t start in the required time… (Event ID 5961)

      Activation via contract helper of the app Microsoft.MSKAPP_8wekyb3d8bbwe!App for the Windows.BackgroundTasks contract failed with Call was canceled by the message filter… (Event ID 5990)

    • Took me twice to log into this using my Microsoft account to post additional details about the crash.

      Faulting application name: microsoftedgecp.exe, version: 11.0.14393.82, time stamp: 0x57a55786
      Faulting module name: wpaxholder.dll, version: 10.0.14393.82, time stamp: 0x57a55c09
      Exception code: 0xc0000602
      Fault offset: 0x00000000000046e9
      Faulting process id: 0x3f10
      Faulting application start time: 0x01d20256e0a8e41d
      Faulting application path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedgecp.exe
      Faulting module path: C:\WINDOWS\SYSTEM32\wpaxholder.dll
      Report Id: 3f0b1c86-a7de-4c92-9fad-8a932e9350d9
      Faulting package full name: Microsoft.MicrosoftEdge_38.14393.0.0_neutral__8wekyb3d8bbwe
      Faulting package-relative application ID: MicrosoftEdge

      Immediately above this in the event log I am now seeing these errors:
      Fault bucket 133371145664, type 5
      Event Name: MoAppCrash
      Response: Not available
      Cab Id: 0

      Problem signature:
      P1: Microsoft.MicrosoftEdge_38.14393.0.0_neutral__8wekyb3d8bbwe
      P2: praid:MicrosoftEdge
      P3: 11.0.14393.82
      P4: 57a55786
      P5: wpaxholder.dll
      P6: 10.0.14393.82
      P7: 57a55c09
      P8: c0000602
      P9: 00000000000046e9
      P10:

      Attached files:
      \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER265D.tmp.WERInternalMetadata.xml

      These files may be available here:
      C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Micros_6b40cfc0e1de7893e4813dc3aa6e570afad95ec_e127e73b_1df7288f

      Analysis symbol:
      Rechecking for solution: 0
      Report Id: 3f0b1c86-a7de-4c92-9fad-8a932e9350d9
      Report Status: 0
      Hashed bucket: 6b850782cc7d7634ad7c1c060a38b10c

    • Can’t reopen. The site is having problems.

    • Home Platform Issues Error
      Something is happening, try again later please, thank you for your patience.

    • Cannot re-open this task and the error message is useless.

    • yep I have experience slow down as well as information from edge that it as dangerous content that edge needed to block. in some of those link ad page of msn. probably that msn need to do a better job on their web site to filter the page that they give link to.

    • as for bryan c androidheadlines.com there is a 404 get error so a url is not working and there is ads trafficking message in the console. seams to be a heavy ads page. that cause slow down not a page that I would return to. to much ads trying to load. since the url is not working it probably try a couple of time to reach the url causing the slow down since there is nothing to load url 404.

    • I’ve been experiencing the same or a very similar problem with ad-heavy sites for quite some time. Edge does not crash for me but simply hangs and needs to be closed with Task Manager. When I check with Process Explorer I see two EdgeContent processes consuming CPU and the consuming thread’s stack traces always have apaxholder.dll and flash.ocx in them. So the culprit seems to be Flash-based ads. It happens for example on heise.de but it depends on the ads displayed because it only occurs sometimes and loading the page a second time usually solves the problem.

      If it helps, I can try to collect detailed stack traces next time it happens.

    • URL: https://s0.2mdn.net/ads/richmedia/studio/pv2/42637957/20160902050047789/banner_728x90.html?e=69&renderingType=2&leftOffset=0&topOffset=0&c=1mw4DIGLkT&t=1

      Windows 10 Desktop Build 14955 x64 (german - DEU)
      Microsoft Edge 39.14955.1000.0
      Microsoft EdgeHTML 15.14955

      C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedgecp.exe

      Problemereignisame: MoAppCrash
      Vollständiger Paketname: Microsoft.MicrosoftEdge_39.14955.1000.0_neutral__8wekyb3d8bbwe
      Anwendungsname: praid:MicrosoftEdge
      Anwendungsversion: 11.0.14955.1000
      Anwendungszeitstempel: 580985dc
      Fehlermodulname: edgehtml.dll
      Fehlermodulversion: 11.0.14955.1000
      Fehlermodulzeitstempel: 58098c59
      Ausnahmecode: 8000ffff
      Ausnahmeoffset: 00000000002e2e27
      Betriebsystemversion: 10.0.14955.2.0.0.256.48
      Gebietsschema-ID: 1031
      Zusatzinformation 1: 2fb2
      Zusatzinformation 2: 2fb25bd6add824cc858594eaf08850e0
      Zusatzinformation 3: c481
      Zusatzinformation 4: c48152fb175ca1896f373e7e87d59573
      Bucket-ID: 4d85df484da381f68c2676937e672182 (133405193485)

      feedback-hub:?contextid=343&feedbackid=ff24dec0-cae3-42d5-b063-c29ba20964e5&form=1&src=2
      https://feedbackhub.link/feedback/343/ff24dec0-cae3-42d5-b063-c29ba20964e5/1/

    • @Dirk F.: No issue with that one, here.

    You need to sign in to your Microsoft account to add a comment.

    Sign in