Community Forums - Message+ for mac OSX freezing

Nicaya2 · ‎01-22-2018

I updated to the latest Mac OSX on my desktop computer and my Message+ app has started freezing/crashing. Basically, I get the pinwheel of death anytime I try to do something. It will last maybe two seconds, I'll be able to type maybe 2 characters, and then the pinwheel starts again. Makes it impossible to use the app. I have tried force quitting and re-opening the app. I have tried Restarting the computer. I have tried checking my OSX is absolutely the latest update (I have High Sierra, 10.13.2). I have tried uninstalling and re-installing Message+ to double-check it is the latest version. Nothing has worked.

Note: this appears to have happened when I updated from the first High Sierra release to the most recent. Given the security fixes, I should not download and install the older version even if I could figure out how to do that.

tgagne · ‎09-14-2019

I just updated to Message+ 2.5.2 and the problem still hasn't disappeared. It hangs so frequently the application is basically useless. Unfortunate, too. The ipad app isn't much better as typing the messages is so slow it's faster just to use my phone. Which is too bad because it's so much smaller.

bldegle2 · ‎09-14-2019

Read the posts here at the forums, the app is BROKEN. No amount of uninstalling and reinstalling will fix the problem across PC platforms(IE Windows and Mac).

Verizon either doesn't care or they have no clue, your choice.

Have a nice day...

vzw_customer_support · ‎09-16-2019

We definitely care about each & every one of our customers, bldegle2. I regret that you feel otherwise. The Message+ Verizon Messages - Windows Desktop application is not compatible with Windows 10 computers. The Windows messaging client for Verizon messages is being temporarily removed to prevent syncing issues and customers should be directed to utilize the messaging web client as a windows alternative. The Message+ team is aware and working on a resolution.

We don't have any reports issues with Macs. When did this start to become a problem? Is your Mac computer software all up to date? What exact errors are you receiving?

You should be able to utilize the messaging web client as an alternative by following the steps in this link
https://www.verizonwireless.com/support/knowledge-base-54302/

AliciaD_VZW

boss055 · ‎10-17-2019

I've been using the Message+ app on my work mac for a few years, and probably about a year ago is when it became useless because it lags and freezes so much, will there ever be a fix??

vzw_customer_support · ‎10-19-2019

I'm sorry you are having issues using the Messages + app on your Mac, boss055. Let's look into this. Have you deleted and redownloaded the app? Have you been able to access the app on another device? If so, what were the results?

JoeL_VZW

waal · ‎12-18-2019

I have a new installation of mesage plus and it still keeps crashing. Are you working on solutions to this?

rainson · ‎01-30-2020

It has been slow for a year or so on my Mac; now it is impossibly slow. Switching back to Apple Messages but not everyone can use that. Please repair Messages+

Thanks,

Ron

vzw_customer_support · ‎02-01-2020

Thanks for these details, Rainson. We do not want to slow you down when it comes to messages. However, did you receive a message about upgrading your Verizon Message + client application? We sent out a message that if you are using an older version of Verizon Message + , you will receive a hard stop asking to have a newer version installed. This was a suggested fix, and you could try it. Here's a link if you wish to upgrade Verizon Message + client application on your Mac computer https://apps.apple.com/us/app/message/id885557198?mt=12 . Does this help?

EdwinW_VZW

lhofm · ‎02-03-2020

It does not help. The latest version is 2.5.2 dated 2016. It runs great on my Android phone but is totally worthless on my Mac Book Pro. Constantly freezing and taking forever just to type a few characters. I'm running macOS Mojave version 10.14.6.

waal · ‎02-04-2020

Still the same with catalina:

Process: Message+ [24307]
Path: /Applications/Message+.app/Contents/MacOS/Message+
Identifier: com.verizon.vzmessagesmac
Version: 2.5.2 (2.5.2)
App Item ID: 885557198
App External ID: 830393432
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Message+ [24307]
User ID: 501

Date/Time: 2020-02-04 10:25:29.333 -0800
OS Version: Mac OS X 10.15.2 (19C57)
Report Version: 12
Anonymous UUID: 7765FFCC-0F4A-125C-A31B-45A24AD4524C

Sleep/Wake UUID: 5E1E41BE-A275-4921-A0B0-4F851177F27D

Time Awake Since Boot: 190000 seconds
Time Since Wake: 90 seconds

System Integrity Protection: enabled

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

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Illegal instruction: 4
Termination Reason: Namespace SIGNAL, Code 0x4
Terminating Process: exc handler [24307]

Application Specific Information:
Crashing on exception: NSTableView error inserting/removing/moving row 44 (numberOfRows: 1).

Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff34a768ab __exceptionPreprocess + 250
1 libobjc.A.dylib 0x00007fff6ab4e805 objc_exception_throw + 48
2 AppKit 0x00007fff325518a1 -[NSTableRowData _throwExceptionForUpdateErrorOnRow:] + 65
3 AppKit 0x00007fff31d07c72 -[NSTableRowData _insertUpdateItem:atIndexes:] + 46
4 AppKit 0x00007fff31c73b89 -[NSTableRowData insertRowsAtIndexes:withRowAnimation:] + 123
5 AppKit 0x00007fff31c739aa -[NSTableView _doUpdatedWorkWithHandler:] + 74
6 AppKit 0x00007fff31c73844 -[NSTableView insertRowsAtIndexes:withAnimation:] + 139
7 Message+ 0x000000010ccc87a5 Message+ + 767909
8 Message+ 0x000000010ccf79ae Message+ + 960942
9 Message+ 0x000000010ccf77eb Message+ + 960491
10 CoreFoundation 0x00007fff349ee037 __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ + 7
11 CoreFoundation 0x00007fff349edebd -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 224
12 Message+ 0x000000010ccf7629 Message+ + 960041
13 CoreFoundation 0x00007fff349f035f __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
14 CoreFoundation 0x00007fff349f02f3 ___CFXRegistrationPost1_block_invoke + 63
15 CoreFoundation 0x00007fff349f0268 _CFXRegistrationPost1 + 372
16 CoreFoundation 0x00007fff349efebe ___CFXNotificationPost_block_invoke + 97
17 CoreFoundation 0x00007fff349bf7e2 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1575
18 CoreFoundation 0x00007fff349bec82 _CFXNotificationPost + 1351
19 Foundation 0x00007fff37044a02 -[NSNotificationCenter postNotificationName:object:userInfo:] + 59
20 CoreData 0x00007fff344cafbb -[NSManagedObjectContext(_NSInternalNotificationHandling) _postObjectsDidChangeNotificationWithUserInfo:] + 747
21 CoreData 0x00007fff3451470c -[NSManagedObjectContext(_NSInternalChangeProcessing) _createAndPostChangeNotification:deletions:updates:refreshes:deferrals:wasMerge:] + 1548
22 CoreData 0x00007fff344c5218 -[NSManagedObjectContext(_NSInternalChangeProcessing) _processRecentChanges:] + 1288
23 CoreData 0x00007fff344c8bd7 -[NSManagedObjectContext save:] + 423
24 Message+ 0x000000010cd83f38 Message+ + 1535800
25 Message+ 0x000000010cc72b53 Message+ + 416595
26 CoreData 0x00007fff344e1059 developerSubmittedBlockToNSManagedObjectContextPerform + 201
27 libdispatch.dylib 0x00007fff6be6350e _dispatch_client_callout + 8
28 libdispatch.dylib 0x00007fff6be6ebc4 _dispatch_main_queue_callback_4CF + 1105
29 CoreFoundation 0x00007fff34a39e00 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
30 CoreFoundation 0x00007fff349f9b8a __CFRunLoopRun + 2370
31 CoreFoundation 0x00007fff349f8bd3 CFRunLoopRunSpecific + 499
32 HIToolbox 0x00007fff3354f65d RunCurrentEventLoopInMode + 292
33 HIToolbox 0x00007fff3354f39d ReceiveNextEventCommon + 600
34 HIToolbox 0x00007fff3354f127 _BlockUntilNextEventMatchingListInModeWithFilter + 64
35 AppKit 0x00007fff31bc0eb4 _DPSNextEvent + 990
36 AppKit 0x00007fff31bbf690 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
37 AppKit 0x00007fff31bb13ae -[NSApplication run] + 658
38 AppKit 0x00007fff31b83775 NSApplicationMain + 777
39 libdyld.dylib 0x00007fff6bebc7fd start + 1
40 ??? 0x0000000000000002 0x0 + 2

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.AppKit 0x00007fff31fa24b7 -[NSApplication _crashOnException:] + 106
1 com.apple.AppKit 0x00007fff31fa239d -[NSApplication reportException:] + 908
2 com.verizon.vzmessagesmac 0x000000010cf2ec14 CLSNSApplicationReportException(objc_object*, objc_selector*, NSException*) + 72
3 com.apple.AppKit 0x00007fff320524d9 uncaughtErrorProc + 145
4 com.apple.CoreFoundation 0x00007fff34aef9f8 __handleUncaughtException + 726
5 libobjc.A.dylib 0x00007fff6ab50784 _objc_terminate() + 90
6 com.verizon.vzmessagesmac 0x000000010cf2e96d 0x10cc0d000 + 3283309
7 libc++abi.dylib 0x00007fff69035dc7 std::__terminate(void (*)()) + 8
8 libc++abi.dylib 0x00007fff69035d79 std::terminate() + 41
9 libdispatch.dylib 0x00007fff6be63522 _dispatch_client_callout + 28
10 libdispatch.dylib 0x00007fff6be6ebc4 _dispatch_main_queue_callback_4CF + 1105
11 com.apple.CoreFoundation 0x00007fff34a39e00 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
12 com.apple.CoreFoundation 0x00007fff349f9b8a __CFRunLoopRun + 2370
13 com.apple.CoreFoundation 0x00007fff349f8bd3 CFRunLoopRunSpecific + 499
14 com.apple.HIToolbox 0x00007fff3354f65d RunCurrentEventLoopInMode + 292
15 com.apple.HIToolbox 0x00007fff3354f39d ReceiveNextEventCommon + 600
16 com.apple.HIToolbox 0x00007fff3354f127 _BlockUntilNextEventMatchingListInModeWithFilter + 64
17 com.apple.AppKit 0x00007fff31bc0eb4 _DPSNextEvent + 990
18 com.apple.AppKit 0x00007fff31bbf690 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
19 com.apple.AppKit 0x00007fff31bb13ae -[NSApplication run] + 658
20 com.apple.AppKit 0x00007fff31b83775 NSApplicationMain + 777
21 libdyld.dylib 0x00007fff6bebc7fd start + 1

Thread 1:: Dispatch queue: IMAP_CONNECTION_TYPE_IDLE (QOS: UNSPECIFIED)
0 libsystem_kernel.dylib 0x00007fff6c0055be __select + 10
1 com.ronge.MailCore 0x000000010d31f959 mailstream_low_ssl_read + 300
2 com.ronge.MailCore 0x000000010d31e78f mailstream_low_read + 37
3 com.ronge.MailCore 0x000000010d31db58 mailstream_feed_read_buffer + 46
4 com.ronge.MailCore 0x000000010d31dfef mailstream_read_line_append + 79
5 com.ronge.MailCore 0x000000010d2e384f -[CTCoreAccount read] + 39
6 com.verizon.vzmessagesmac 0x000000010cc462d8 0x10cc0d000 + 234200
7 com.verizon.vzmessagesmac 0x000000010cc45c4d 0x10cc0d000 + 232525
8 com.verizon.vzmessagesmac 0x000000010cc4551f 0x10cc0d000 + 230687
9 com.apple.Foundation 0x00007fff3707c52e __NSOPERATIONQUEUE_IS_STARTING_AN_OPERATION__ + 17
10 com.apple.Foundation 0x00007fff3707c3f8 __NSOQSchedule_f + 182
11 libdispatch.dylib 0x00007fff6be6f134 _dispatch_block_async_invoke2 + 83
12 libdispatch.dylib 0x00007fff6be6350e _dispatch_client_callout + 8
13 libdispatch.dylib 0x00007fff6be656c0 _dispatch_continuation_pop + 414
14 libdispatch.dylib 0x00007fff6be64dbe _dispatch_async_redirect_invoke + 703
15 libdispatch.dylib 0x00007fff6be717e2 _dispatch_root_queue_drain + 326
16 libdispatch.dylib 0x00007fff6be71f22 _dispatch_worker_thread2 + 92
17 libsystem_pthread.dylib 0x00007fff6c0bd6b6 _pthread_wqthread + 220
18 libsystem_pthread.dylib 0x00007fff6c0bc827 start_wqthread + 15

Thread 2:: com.twitter.crashlytics.mac.MachExceptionServer
0 libsystem_kernel.dylib 0x00007fff6c00005a write + 10
1 com.verizon.vzmessagesmac 0x000000010cf250fe CLSSDKFileLog + 414
2 com.verizon.vzmessagesmac 0x000000010cf1c821 0x10cc0d000 + 3209249
3 libsystem_pthread.dylib 0x00007fff6c0c0e65 _pthread_start + 148
4 libsystem_pthread.dylib 0x00007fff6c0bc83b thread_start + 15

Thread 3:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x00007fff6bffd25a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff6bffd5d0 mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff349fad0b __CFRunLoopServiceMachPort + 322
3 com.apple.CoreFoundation 0x00007fff349f98e7 __CFRunLoopRun + 1695
4 com.apple.CoreFoundation 0x00007fff349f8bd3 CFRunLoopRunSpecific + 499
5 com.apple.CFNetwork 0x00007fff3315f012 0x7fff33115000 + 303122

waal · ‎02-04-2020

THis is not an adequate response:

I contiually have this issue with an updated Mac, now running Catalina: