Uploaded image for project: 'HipChat'
  1. HipChat
  2. HCPUB-2770

Windows client receives "QtWebEngineProcess has stopped working" error after unlocking your account or undocking the device when you have multiple screens/external displays

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Low Low
    • None
    • None
    • None
    • Severity 3 - Minor

      Summary

      Windows client receives "QtWebEngineProcess has stopped working" error after unlocking your account or undocking the device when you have multiple screens/external displays

      Environment

      HipChat Client: 4.29.5.1662
      Windows 10 Enterprise x64
      Device: Surface Pro 4 i5 with Intel HD 520 (20.19.15.4463)
      Screens: 2x HP z24 Display, HipChat is running on the Surface screen
      Faulting application name: QtWebEngineProcess.exe, version: 0.0.0.0, time stamp: 0x57c99994
      Faulting module name: Qt5WebEngineCore.dll, version: 5.7.0.0, time stamp: 0x57c9994a
      Exception code: 0x80000003
      Fault offset: 0x00b5c3e1
      Faulting process id: 0xd3a0
      Faulting application start time: 0x01d2918f974b6b2d
      Faulting application path: C:\Program Files (x86)\Atlassian\HipChat4\QtWebEngineProcess.exe
      Faulting module path: C:\Program Files (x86)\Atlassian\HipChat4\Qt5WebEngineCore.dll
      Report Id: 56fa9d8f-78b6-4722-bc19-b64f599ec5eb
      Faulting package full name:
      Faulting package-relative application ID:

      Steps to Reproduce

      1. Dock Surface Pro 4 with multiple external displays
      2. Login to HipChat and chat as usual
      3. Lock your machine's account then unlock it or undock the device

      Actual Results

      HipChat Windows client is running as usual

      Expected Results

      HipChat Windows client started to become unresponsive after you unlock your machine's account or undock the device. You will need to restart the client and it will be fine again until the next account unlock or undocking the device.

      Notes

      The same problem is not observed when multiple screens/external displays are not in use

              Unassigned Unassigned
              hsuhailah Hanis Suhailah (Inactive)
              Archiver:
              mandreacchio Michael Andreacchio

                Created:
                Updated:
                Resolved:
                Archived: