Installed Web App crashes when trying to launch it

Browser Support Desktop Support
1

Description of the issue

Installed WebApp crashes when trying to open it.

Steps to Reproduce

  1. Go to https://brave-bug.ces.rocks/
  2. Make sure you don’t have Javascript disabled for the page.
  3. Once the page is loaded, wait a moment until the manifest.json and the service worker are loaded.
  4. Once that’s ready you should be able to click on the hamburger button and see an Open in Test WebApp menu entry. Click it.
  5. Click Install on the “Install App?” dialog.
  6. Tab closes, Apps folder opens in Finder (on Mac), webapp is launched and crashes instantly. Reproduces every time.

Actual Result

Here’s what the crash looks like:

50
50830×482 103 KB

Here’s the report generated:

Process:               app_mode_loader [43828]
Path:                  /Users/USER/*/Test WebApp.app/Contents/MacOS/app_mode_loader
Identifier:            com.brave.Browser.app.Default-ecibhmkcfkfmbgikigfipjggblfchmje
Version:               2019.5.8.53090 (63.55)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           app_mode_loader [43828]
User ID:               501

Date/Time:             2019-05-08 16:26:33.767 -0300
OS Version:            Mac OS X 10.14.4 (18E226)
Report Version:        12
Anonymous UUID:        37B7D812-FFF8-4D75-0CB2-22E5C7843A0A

Sleep/Wake UUID:       4360407E-0188-4FDB-B089-17E818252781

Time Awake Since Boot: 1100000 seconds
Time Since Wake:       440000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Trace/BPT trap: 5
Termination Reason:    Namespace SIGNAL, Code 0x5
Terminating Process:   exc handler [43828]

Application Specific Information:
dyld2 mode

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.brave.Browser.app.Default-ecibhmkcfkfmbgikigfipjggblfchmje  0x00000001058c6444 0x105704000 + 1844292
1   com.brave.Browser.app.Default-ecibhmkcfkfmbgikigfipjggblfchmje  0x0000000105706413 0x105704000 + 9235
2   com.brave.Browser.app.Default-ecibhmkcfkfmbgikigfipjggblfchmje  0x000000010570605b main + 27
3   libdyld.dylib                   0x00007fff58d743d5 start + 1

Thread 1:
0   libsystem_pthread.dylib         0x00007fff58f613f0 start_wqthread + 0

Thread 2:
0   libsystem_pthread.dylib         0x00007fff58f613f0 start_wqthread + 0

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x00007fff8bd6e9a0  rcx: 0x0000000000000000  rdx: 0x0000000000000400
  rdi: 0x00007ffeea4fb240  rsi: 0x00007fdcf4e0bdb0  rbp: 0x00007ffeea4fb710  rsp: 0x00007ffeea4fb1e0
   r8: 0x00000000000130a8   r9: 0x00007fff8bd6e048  r10: 0x0000000000000000  r11: 0x00007fff8bd6e040
  r12: 0x00007fdcf4e0bdb0  r13: 0x00007ffeea4fb228  r14: 0x00007ffeea4fb820  r15: 0x00007ffeea4fb830
  rip: 0x00000001058c6444  rfl: 0x0000000000000246  cr2: 0x00007fff8bd71260
  
Logical CPU:     2
Error Code:      0x00000000
Trap Number:     3

[ Continuing report in topic comments because topics have 30000 character limit]

Operating System and Brave Version

MacOS Mojave 10.14.4 (18E226)
Brave Version 0.63.55 Chromium: 74.0.3729.131 (Official Build) (64-bit)

Additional Notes

This works like a charm on Chrome. Which leads me to think that this is a Brave issue.

That’s all. Thanks for all the great work.

2

@Mattches please take a look

4

@ces,
Thank you for reaching out – great write-up.
I believe this is due to an open issue we have for PWAs on desktop:

I’ve added your report to the thread linked above as a +1 on your behalf.

5

The problem on Windows is that the link is pointing to the wrong executable. Seems easy to fix. This problem on Mac is mentioned on that issue but I’m not sure it’s the same problem or close to the same.

Should I do anything with all this? This is my first bug report, not sure how to proceed.

1 Like
6

@ces,
Excellent first report!
Nothing you need to do at this point – while rather unsatisfying, we’ll have to wait until the issue is reviewed and resolved by devs.

I’ve reached out to some team members internally – a gentle nudge to get some eyes on it. Hopefully we’ll have more information on this soon.

Unless there’s any other questions surrounding this particular issue I’m going to close this thread out. If you have other issues or concerns, please don’t hesitate to create a new topic and we’d be happy to help.

1 Like