Edge crashes at github.com/features

Fixed Issue #11242388

Details

Author
Dirk F.
Created
Mar 12, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
15.15048
Reports
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

1.  Get a large monitor, maximize, and navigathttps://github.com/features](https://github.[https://github.com/features](https://github.com/features)

See crash dump.

 

 

https://github.com/features = crashing (mostly) - Extensions = no active extension - about:flags = default values - tested on different devices - Windows 10 x64 Build 15048 & 15055 For more info see Feedback-Hub (de-de / germany) entry: https://aka.ms/j9wqtn Source Microsoft Edge Summary Stopped working Date ‎3/‎12/‎2017 12:56 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_40.15055.0.0_neutral__8wekyb3d8bbwe Application Name: praid:ContentProcess Application Version: 11.0.15055.0 Application Timestamp: 58bf6e30 Fault Module Name: edgehtml.dll Fault Module Version: 11.0.15055.0 Fault Module Timestamp: e7504fc8 Exception Code: 80070057 Exception Offset: 0000000000a25d32 OS Version: 10.0.15055.2.0.0.768.101 Locale ID: 1033 Additional Information 1: 7b81 Additional Information 2: 7b81dfe24037b8691f4781f1165686af Additional Information 3: ddb0 Additional Information 4: ddb0a96f6843ff59a939d9e42584a60f Extra information about the problem Bucket ID: 88883c1fa5377daf4b2625a1bd6063c9 (133471953607)

Attachments

Comments and activity

  • Changed Steps to Reproduce

    Changed Steps to Reproduce

    Changed Steps to Reproduce

  • Build 15058 too:

    Quelle
    Microsoft Edge

    Zusammenfassung
    Nicht mehr funktionsfähig

    Datum
    ‎15.‎03.‎2017 19:47

    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_40.15058.0.0_neutral__8wekyb3d8bbwe
    Anwendungsname: praid:ContentProcess
    Anwendungsversion: 11.0.15058.0
    Anwendungszeitstempel: 58c35690
    Fehlermodulname: edgehtml.dll
    Fehlermodulversion: 11.0.15058.0
    Fehlermodulzeitstempel: b2f9e26b
    Ausnahmecode: 80070057
    Ausnahmeoffset: 0000000000a3bf12
    Betriebsystemversion: 10.0.15058.2.0.0.256.48
    Gebietsschema-ID: 1031
    Zusatzinformation 1: 7b81
    Zusatzinformation 2: 7b81dfe24037b8691f4781f1165686af
    Zusatzinformation 3: 06ea
    Zusatzinformation 4: 06eadb111722a8a7a1a3933b8b9e8dac

    Weitere Informationen über das Problem
    Bucket-ID: 8247a2cee66e4d02d8cd509b0699ba94 (133473578311)

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

  • Happens for me on 15061.

  • Microsoft Edge Team

    Changed Assigned To to “Rico M.”

    Changed Assigned To from “Rico M.” to “Lee H.”

  • Update:
    Still the same with build 15063 and 16176 on different devices (notebook & desktop).
    Feedback-Hub (en-us) with captures = https://aka.ms/Rirl9f

  • Changed Steps to Reproduce

  • My devices are:
    PrimaryPC: ASRock X99M Extreme4; i7-5820K; 4x4GB DDR4-2400; Gigabyte GTX 1060 6GB Mini OC; Samsung 950 Pro 512 GB
    SecondaryPC: Asus M4N82 Deluxe; Phenom II x6 1090T; 4x2GB DDR2-800; GeForce GT530
    Convertible: Lenovo Yoga 710-14IKB; i5-7200U [HD620]; 1x8GB DDR4-2400; 256GB SSD
    Notebook: ASUS K53SV; i5-2410m [HD3000]; 2x4GB DDR3-1866; GeForce 540M 2GB; 850 EVO 500 GB

  • Microsoft Edge Team

    Changed Status to “Confirmed”

    Changed Status from “Confirmed”

    Changed Assigned To to “Cory H.”

  • Today I found out, that it is only crashing, if the icons (screenshot) “Code review, Project management, Integrations, Community management, Documentation and Code hosting” are visible. It depends on the window size of the Edge browser, if they will be displayed or not. So if the window is maximized it will crashing. If the window has a small size it will not crashing.

  • Microsoft Edge Team

    Changed Assigned To from “Cory H.” to “Tim K.”

    Changed Assigned To to “Dave B.”

    Changed Assigned To from “Dave B.” to “Michael E.”

    Changed Steps to Reproduce

    Changed Steps to Reproduce

    Changed Assigned To to “Christian F.”

    Changed Assigned To from “Christian F.” to “Sergey M.”

    Changed Status to “Confirmed”

    Changed Assigned To from “Sergey M.” to “Rick J.”

    Changed Status from “Confirmed” to “Fixed”

  • Thanks for reporting this. Fixed in internals builds and will be included in an upcoming release.

  • Changed Status from “Fixed”

  • It is still crashing with build 16226 and 16232.

    Quelle
    Microsoft Edge

    Zusammenfassung
    Nicht mehr funktionsfähig

    Datum
    ‎29.‎06.‎2017 10:08

    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_41.16232.1000.0_neutral__8wekyb3d8bbwe
    Anwendungsname: praid:ContentProcess
    Anwendungsversion: 11.0.16232.1000
    Anwendungszeitstempel: 594f0875
    Fehlermodulname: edgehtml.dll
    Fehlermodulversion: 11.0.16232.1000
    Fehlermodulzeitstempel: f65aad2b
    Ausnahmecode: 80070057
    Ausnahmeoffset: 0000000000a68aba
    Betriebsystemversion: 10.0.16232.2.0.0.256.48
    Gebietsschema-ID: 1031
    Zusatzinformation 1: 7ff6
    Zusatzinformation 2: 7ff65d15c72065d9acef170eae1c8683
    Zusatzinformation 3: 4fdd
    Zusatzinformation 4: 4fdd325a0300864f6fc6d57df613b89b

    Weitere Informationen über das Problem
    Bucket-ID: 7abf08d5201c04c8683f137fd9b40949 (133519343591)

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

    Changed Status to “Fixed”

  • Hello,

    Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge and will be available in an upcoming Insider Preview build.

    Best Wishes,
    The MS Edge Team

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

Sign in