Crash on launch of latest Vivaldi version on Mac
-
@eb303 Thanks for picking up on the hint.
In this case, it was fortunate that the fix was to apply the same permission change to every symlink in the bundle. -
FYI, I also raised this issue as feedback to the Vivaldi 1.10.834.9 Snapshot release. Vivaldi replied that they "are fully aware if it."
Here's a link to my post: https://forum.vivaldi.net/post/134807
You can also read the full thread (it's at the top of the comments section) here: https://vivaldi.com/blog/snapshots/sorting-of-downloads-vivaldi-browser-snapshot-1-10-834-9/
Hopefully a fix is in the works.
-
FYI, this issue was fixed in the Vivaldi 1.10.838.7 snapshot that was released earlier today. Unfortunately, Vivaldi 1.9 is still broken, and also in need of updating because Chromium 58.0.3029.110 just got released this afternoon too.
-
@xyzzy OK, thanks a lot for the updates.
As long as the dirty hack works for v1.9, I'm happy, though. 
And at least, the developers are aware of the issue now, so I guess the next release will have it fixed, that's the most important. -
Mac builds are now fixed on both the Snapshot and Stable channels. If you don't have any objections, I'm marking this thread Resolved.
Cheers!
-
@xyzzy Downloaded and installed the latest version: it works indeed, no problem at all.
Thanks again! -
I am having the same problem today.. Vivaldi got updated on MAC and then when i try to open each time it crashed. Tried reinstalling.. did not work.. i loved to use vivaldi as my main browser.. not i am sad that its doing this way
I can share the dump if required.
-
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 com.vivaldi.Vivaldi.framework 0x000000010d5a41b7 ChromeMain + 93788295
1 com.vivaldi.Vivaldi.framework 0x000000010d5abcbb ChromeMain + 93819787
2 com.vivaldi.Vivaldi.framework 0x000000010c96b3fb ChromeMain + 80972491
3 com.vivaldi.Vivaldi.framework 0x000000010c96b99d ChromeMain + 80973933
4 com.vivaldi.Vivaldi.framework 0x000000010acaa62f ChromeMain + 50822399
5 com.vivaldi.Vivaldi.framework 0x000000010acba7fb ChromeMain + 50888395
6 com.vivaldi.Vivaldi.framework 0x000000010acba59b ChromeMain + 50887787
7 com.vivaldi.Vivaldi.framework 0x000000010ad14a21 ChromeMain + 51257585
8 com.vivaldi.Vivaldi.framework 0x000000010ad0f22a ChromeMain + 51235066
9 com.vivaldi.Vivaldi.framework 0x000000010ad142ef ChromeMain + 51255743
10 com.apple.CoreFoundation 0x00007fff47b3bd13 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17
11 com.apple.CoreFoundation 0x00007fff47b3bcb9 __CFRunLoopDoSource0 + 108
12 com.apple.CoreFoundation 0x00007fff47b1f67f __CFRunLoopDoSources0 + 195
13 com.apple.CoreFoundation 0x00007fff47b1ec49 __CFRunLoopRun + 1189
14 com.apple.CoreFoundation 0x00007fff47b1e552 CFRunLoopRunSpecific + 455
15 com.apple.HIToolbox 0x00007fff46d7d1ab RunCurrentEventLoopInMode + 292
16 com.apple.HIToolbox 0x00007fff46d7cee5 ReceiveNextEventCommon + 603
17 com.apple.HIToolbox 0x00007fff46d7cc76 _BlockUntilNextEventMatchingListInModeWithFilter + 64
18 com.apple.AppKit 0x00007fff4511477d _DPSNextEvent + 1135
19 com.apple.AppKit 0x00007fff4511346b -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1361
20 com.vivaldi.Vivaldi.framework 0x000000010a7c3d30 ChromeMain + 45683712
21 com.vivaldi.Vivaldi.framework 0x000000010ad0f22a ChromeMain + 51235066
22 com.vivaldi.Vivaldi.framework 0x000000010a7c3c69 ChromeMain + 45683513
23 com.apple.AppKit 0x00007fff4510d588 -[NSApplication run] + 699
24 com.vivaldi.Vivaldi.framework 0x000000010ad1523c ChromeMain + 51259660
25 com.vivaldi.Vivaldi.framework 0x000000010ad13ca2 ChromeMain + 51254130
26 com.vivaldi.Vivaldi.framework 0x000000010acbad83 ChromeMain + 50889811
27 com.vivaldi.Vivaldi.framework 0x000000010ac90fe3 ChromeMain + 50718387
28 com.vivaldi.Vivaldi.framework 0x000000010a7cfdcf ChromeMain + 45733023
29 com.vivaldi.Vivaldi.framework 0x0000000108b890bb ChromeMain + 16082827
30 com.vivaldi.Vivaldi.framework 0x0000000108b8ab82 ChromeMain + 16089682
31 com.vivaldi.Vivaldi.framework 0x0000000108b86928 ChromeMain + 16072696
32 com.vivaldi.Vivaldi.framework 0x000000010a71b3af ChromeMain + 44993151
33 com.vivaldi.Vivaldi.framework 0x000000010a71b03b ChromeMain + 44992267
34 com.vivaldi.Vivaldi.framework 0x000000010d008908 ChromeMain + 87908312
35 com.vivaldi.Vivaldi.framework 0x000000010a71a674 ChromeMain + 44989764
36 com.vivaldi.Vivaldi.framework 0x0000000107c329eb ChromeMain + 187
37 com.vivaldi.Vivaldi 0x0000000100f3798f main + 287
38 libdyld.dylib 0x00007fff73a9d3d5 start + 1 -
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00007ffeeecc6678 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x00007fd8a4e2a6a0 rsi: 0x00007fd8a42f87c0 rbp: 0x00007ffeeecc6600 rsp: 0x00007ffeeecc6570
r8: 0x000000008a61c1a4 r9: 0x00000000ffffff0f r10: 0x00007fd8a6100000 r11: 0x00000000013986c0
r12: 0x00007fd8a6194c90 r13: 0x00007fd8a4e2b7c0 r14: 0x00007fd8a6138b30 r15: 0x00007fd8a42410c0
rip: 0x000000010d5a41b7 rfl: 0x0000000000010246 cr2: 0x0000000000000008 -
@Gwen-Dragon how can i start vivaldi on MAC with disabling all extensions.. i am unable to use it now..i just wanted to try without extensions
-
@Gwen-Dragon submitted the bug #VB-71330
-
Ppafflick moved this topic from Vivaldi for macOS on
