Edge crashes at https://ballotpedia.org/Sample_Ballot_Lookup

Won’t fix Issue #9729083

Details

Author
Dirk F.
Created
Nov 9, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
15.14959
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

STR:
a) open https://ballotpedia.org/Sample_Ballot_Lookup with Edge -> crash

Source
Microsoft Edge

Summary
Stopped working

Date
‎11/‎9/‎2016 11:47 AM

Status
Report sent

Description
Faulting Application Path: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedgecp.exe

Problem signature
Problem Event Name: MoAppCrash
Package Full Name: Microsoft.MicrosoftEdge_39.14959.1000.0_neutral__8wekyb3d8bbwe
Application Name: praid:MicrosoftEdge
Application Version: 11.0.14959.1000
Application Timestamp: 58116bfb
Fault Module Name: edgehtml.dll
Fault Module Version: 11.0.14959.1000
Fault Module Timestamp: 581171d3
Exception Code: 86664004
Exception Offset: 000000000030dbd7
OS Version: 10.0.14959.2.0.0.256.48
Locale ID: 1033
Additional Information 1: bee2
Additional Information 2: bee27f4df7c57d9ee8caad6ae6d633ce
Additional Information 3: affe
Additional Information 4: affe111c4310274bdee5e5252f7d7d68

Extra information about the problem
Bucket ID: 11af4fc156bd95244eaf8af0668c0534 ()

Feedback Hub:
http://aka.ms/H4ydw0
feedback-hub:?contextid=356&feedbackid=edbfe3f5-4ff3-4883-bee0-90f7541c1845&form=1&src=1

Attachments

Comments and activity

  • Build 14393.447 is also crashing:

    Quelle
    Microsoft Edge

    Zusammenfassung
    Nicht mehr funktionsfähig

    Datum
    ‎09.‎11.‎2016 12:59

    Status
    Der Bericht wurde gesendet.

    Beschreibung
    Pfad der fehlerhaften Anwendung: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\microsoftedgecp.exe

    Problemsignatur
    Problemereignisame: MoAppCrash
    Vollständiger Paketname: Microsoft.MicrosoftEdge_38.14393.0.0_neutral__8wekyb3d8bbwe
    Anwendungsname: praid:MicrosoftEdge
    Anwendungsversion: 11.0.14393.82
    Anwendungszeitstempel: 57a55786
    Fehlermodulname: edgehtml.dll
    Fehlermodulversion: 11.0.14393.447
    Fehlermodulzeitstempel: 5819c228
    Ausnahmecode: 86664004
    Ausnahmeoffset: 0000000000407552
    Betriebsystemversion: 10.0.14393.2.0.0.768.101
    Gebietsschema-ID: 1031
    Zusatzinformation 1: 8280
    Zusatzinformation 2: 8280d2c493e4841c2ca76c6b7d5d6ca0
    Zusatzinformation 3: 1149
    Zusatzinformation 4: 1149b405058e84fd621af3b4d912c764

    Weitere Informationen über das Problem
    Bucket-ID: 0421bc81523d28cfe6ce2088fba0216b (133422116804)

  • Microsoft Edge Team

    Changed Assigned To to “Ibrahim O.”

    Changed Status to “Fixed”

  • Thank you for your feedback. Looks like that is a temporary bug that introduced in a specific Insider preview build which is already fixed in in our internal builds. You should be able to see that fix in upcoming first or second Insider preview updates. I will close this bug as fixed for now, but please feel free to reactivate the bug if you see that issue persists in next updates. 

    All the best,
    The MS Edge Team  

  • Changed Status from “Fixed”

  • It is still crashing for me with build 14986 (without any extension).

    Quelle
    Microsoft Edge

    Zusammenfassung
    Nicht mehr funktionsfähig

    Datum
    ‎08.‎12.‎2016 13:53

    Status
    Der Bericht wurde gesendet.

    Beschreibung
    Pfad der fehlerhaften Anwendung: C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe

    Problemsignatur
    Problemereignisame: MoAppCrash
    Vollständiger Paketname: Microsoft.MicrosoftEdge_39.14986.1000.0_neutral__8wekyb3d8bbwe
    Anwendungsname: praid:ContentProcess
    Anwendungsversion: 11.0.14986.1000
    Anwendungszeitstempel: 58427898
    Fehlermodulname: edgehtml.dll
    Fehlermodulversion: 11.0.14986.1000
    Fehlermodulzeitstempel: 4b020f60
    Ausnahmecode: 86664004
    Ausnahmeoffset: 0000000000469c97
    Betriebsystemversion: 10.0.14986.2.0.0.256.48
    Gebietsschema-ID: 1031
    Zusatzinformation 1: 1bd8
    Zusatzinformation 2: 1bd840e6d3d9d69c27319d70eb92b70a
    Zusatzinformation 3: 2296
    Zusatzinformation 4: 2296b445baf9326a0739ed2fe813b46d

    Weitere Informationen über das Problem
    Bucket-ID: da37784d5ef3defc6837ef9a6f18dced (133435659878)

  • Microsoft Edge Team

    Changed Assigned To to “Brad E.”

    Changed Assigned To to “Rico M.”

    Changed Steps to Reproduce

    Changed Assigned To from “Rico M.” to “Brad E.”

    Changed Status to “Confirmed”

  • Thanks for letting us know, Dirk. But we need more details in order to consider this more actionable.

    We would need a dxdiag on the affected machine to start with. The sooner you can provide that the sooner we can start digging further.

  • Microsoft Edge Team

    Changed Assigned To from “Brad E.” to “Rico M.”

  • OK using the information you gave me I was able to look up information about the crashes you have experienced.  Unfortunately all the reported crash dates for this particular bug are too long ago and don’t match the dates of other crashes.  I can’t be sure that the bugs we have based on crashes from your device are covering this particular issue because it’s been too long.  This might be a different issue or it could be in the list arleady.

     

    However, if you can still make it fail,  what I’d like you to do is make it fail A LOT.  Let it crash and upload the crash information.   Update this bug and when that happens I should be able to see if this is a unique failure or if it’s already covered by existing failures.  Right now there are 4 distinct sources of crashes coming from your machine all of which have specific information.  If we can confirm this bug is one of those, or a new one, we’ll have a chance to fix it.

     

    Unfortunately, the URL you provide just works for me.  I can’t make it fail.  Alas, that would have been too easy I guess.

     

    Thank you for your patience.

  • Microsoft Edge Team

    Changed Status from “Confirmed” to “Won’t fix”

  • I’m convinced I’ve found a duplicate bug with crash dumps, linking them up.

  • With build 15007 and 15014 it is working for me. Thank you.

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

Sign in