MySQL Bugs: #97449: Results grid blank on MacOS Catalina (10.15.1) using Workbench build 8.0.18

Bug #97449	Results grid blank on MacOS Catalina (10.15.1) using Workbench build 8.0.18
Submitted:	31 Oct 2019 21:09	Modified:	3 Dec 2019 16:32
Reporter:	James BonTempo	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	8.0.18	OS:	MacOS (Catalina (10.15.1))
Assigned to:		CPU Architecture:	Any

Description:
A successfully executed SELECT query does not produce results in the Results Grid. This bug makes Workbench essentially unusable.

How to repeat:
Execute a SELECT query.

Result Grid showing data

Attachment: 97449.png (image/png, text), 290.31 KiB.

Thank you for the bug report. I couldn't repeat please see prior attached screenshot.

https://bugs.mysql.com/bug.php?id=97457 marked as duplicate of this one.

Screenshot clearly showing a successfully execute SELECT query but no Results Grid

Attachment: Workbench Sreenshot.png (image/png, text), 241.25 KiB.

This has clearly been an issue for other people using the same Workbench build on other MacOS versions. For example, see https://bugs.mysql.com/bug.php?id=87714

Scroll to the end of the thread on that bug to see a recent comment (2019-08-28) re: the same issue with build 8.0.17 on MacOS Mojave (10.14.6).

Also see https://bugs.mysql.com/bug.php?id=91265 as proof that this is a recurring issue regardless of whether you can reproduce it or not.

The only way I could see the result grid is "blank" or "hidden" is when it was resized until the bottom, if you place the mouse pointer at the bottom of the grid space so it changes the pointer ( like a cross) and holding try to resize it up.

Result Grid Hidden when resized all at the bottom

Attachment: grid-blank.png (image/png, text), 373.41 KiB.

Workbench with blank Results Grid area

Attachment: Workbench with blank Results Grid area.png (image/png, text), 271.49 KiB.

Yeah, I tried that already. The area that was exposed after doing that was blank. See the screenshot I uploaded...

The only way I've been able to see a Results Grid is by first EXPLAINING the statement then clicking on the Results Grid (vertical) tab all the way to the right. BTW, I tried this based on some of the comments to the previous versions of this bug that I have linked to above.

Workbench EXPLAIN with Results Grid

Attachment: Workbench EXPLAIN with Results Grid.png (image/png, text), 302.74 KiB.

Hi James,

I tested the steps in 4 different Workbench versions (6.3.10, 8.0.13, 8.0.17 and a fresh build from the code repository) and neither one showed the effect you are describing. I don't say you are wrong, certainly not, but if we cannot repoduce the problem, how can we fix it?

When this problem occurs the first time, what do you see in the log file (Help -> Show Log File)? Any error shown there or something that seems related to the issue? Also, if you are comfortable with the macOS Konsole.app, run that and watch it while running a query in WB when no result set comes up. Do you see an error there, related to Workbench?

What's the simplest list of steps to make this issue show up for you?

Thanks

Thanks, Mike.

The simplest list of steps to recreate this issue is:
1. Open Workbench
2. Connect to a data source.
3. Execute a SELECT query.

I don't have to do anything other than these most basic things.

After executing a query following the steps above, there are no errors in the log file. However, when I tried to execute the query a second time it simply hung (the progress indicator is actually still spinning as I write this). I found this line when "tailing" the log file:

[ERR][      WBContext]: WBContext: exception in flush idle task: Exception: mforms: attempt to add a subview already contained somewhere

I found the following Fault (also reported as an Error) in the Console app:

CoreUI: error void DrawQualifiedAnimationFrameWithOperation(CFIndex (^)(NSInteger), NSRect, CUIThemeRendition *, CGContextRef, CGBlendMode, CGFloat, CUIFocusRingType, CGColorRef) got a invalid subimage '{{1, 126}, {20, 16}}' for rendition <_CUIInternalLinkRendition: 0x7fc035648520> -- Rendition name: ProgressIndicatorCircular_Indeterminate_Small.psd

And these Errors:

*** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[0]

(
	0   CoreFoundation                      0x00007fff37196f53 __exceptionPreprocess + 250
	1   libobjc.A.dylib                     0x00007fff6d25c835 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff37259d3a _CFThrowFormattedException + 202
	3   CoreFoundation                      0x00007fff372647cb -[__NSPlaceholderDictionary initWithObjects:forKeys:count:].cold.5 + 0
	4   CoreFoundation                      0x00007fff370b37cd -[__NSPlaceholderDictionary initWithObjects:forKeys:count:] + 235
	5   CoreFoundation                      0x00007fff370efb06 +[NSDictionary dictionaryWithObjects:forKeys:count:] + 59
	6   libmforms.dylib                     0x000000010c54e4d8 _ZL19util_get_text_widthRKNSt3__112basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEES7_ + 531
	7   libwbprivate.be.dylib               0x000000010baac2a0 _ZN15SqlEditorResult25get_autofit_column_widthsEP9Recordset + 262
	8   libwbprivate.be.dylib               0x000000010baa740e _ZN15SqlEditorResult26restore_grid_column_widthsEv + 940
	9   libwbprivate.be.dylib               0x000000010baa498a _ZN15SqlEditorResult13set_recordsetENSt3__110shared_ptrI9RecordsetEE + 3308
	10  libwbprivate.be.dylib               0x000000010ba7bbba _ZN14SqlEditorPanel23add_panel_for_recordsetENSt3__110shared_ptrI9RecordsetEE + 106
	11  libwbprivate.be.dylib               0x000000010ba7ba63 _ZN14SqlEditorPanel33add_panel_for_recordset_from_mainENSt3__110shared_ptrI9RecordsetEE + 361
	12  libwbprivate.be.dylib               0x000000010ba84c0a _ZNSt3__128__invoke_void_return_wrapperIvE6__callIJRNS_6__bindIM14SqlEditorPanelFvNS_10shared_ptrI9RecordsetEEEJPS4_RS7_EEEEEEvDpOT_ + 70
	13  libwbpublic.be.dylib                0x000000010af8f512 _ZNK5boost8signals26detail20slot_call_iterator_tINS1_21variadic_slot_invokerINS1_9void_typeEJEEENSt3__115__list_iteratorINS_10shared_ptrINS1_15connection_bodyINS6_4pairINS1_15slot_meta_groupENS_8optionalIiEEEENS0_4slotIFvvENS_8functionISG_EEEENS0_5mutexEEEEEPvEESL_E11dereferenceEv + 50
	14  libwbpublic.be.dylib                0x000000010afa4e52 _ZNK5boost8signals219optional_last_valueIvEclINS0_6detail20slot_call_iterator_tINS4_21variadic_slot_invokerINS4_9void_typeEJEEENSt3__115__list_iteratorINS_10shared_ptrINS4_15connection_bodyINS9_4pairINS4_15slot_meta_groupENS_8optionalIiEEEENS0_4slotIFvvENS_8functionISJ_EEEENS0_5mutexEEEEEPvEESO_EEEEvT_ST_ + 46
	15  libwbpublic.be.dylib                0x000000010b0f244d _ZN5boost8signals26detail11signal_implIFvvENS0_19optional_last_valueIvEEiNSt3__14lessIiEENS_8functionIS3_EENS9_IFvRKNS0_10connectionEEEENS0_5mutexEEclEv + 501
	16  libwbpublic.be.dylib                0x000000010afbfd63 _ZN3bec10GRTManager18perform_idle_tasksEv + 391
	17  libwbprivate.be.dylib               0x000000010b804589 _ZN2wb9WBContext16flush_idle_tasksEb + 41
	18  MySQLWorkbench                      0x000000010aa9c340 -[WBMainController flushIdleTasks:] + 66
	19  Foundation                          0x00007fff3988d1cb __NSFirePerformWithOrder + 360
	20  CoreFoundation                      0x00007fff3714266e __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
	21  CoreFoundation                      0x00007fff37142594 __CFRunLoopDoObservers + 457
	22  CoreFoundation                      0x00007fff370e572b __CFRunLoopRun + 1219
	23  CoreFoundation                      0x00007fff370e4fe3 CFRunLoopRunSpecific + 499
	24  HIToolbox                           0x00007fff35c6c67d RunCurrentEventLoopInMode + 292
	25  HIToolbox                           0x00007fff35c6c3bd ReceiveNextEventCommon + 600
	26  HIToolbox                           0x00007fff35c6c147 _BlockUntilNextEventMatchingListInModeWithFilter + 64
	27  AppKit                              0x00007fff342f1864 _DPSNextEvent + 990
	28  AppKit                              0x00007fff342f05d4 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352
	29  AppKit                              0x00007fff342ead76 -[NSApplication run] + 658
	30  AppKit                              0x00007fff342dc95d NSApplicationMain + 777
	31  libdyld.dylib                       0x00007fff6e5bf2e5 start + 1
	32  ???                                 0x0000000000000001 0x0 + 1
)

Thanks for the error print. It looks like you have trouble with the column width cache. Workbench tries to restore column widths in result sets, where possible, and uses a cache stored on disk. This might have been corrupted.

To check if that's the culprit open Workbench, go to Help -> Locate Log Files. This will open a finder window with the WB log files. Go up one level in the file system to get to the main WB data folder. There you will see a `cache` folder. Rename that and restart Workbench. Does this fix the result set problem?

Workbench will automatically recreate that folder, but if you need your query history for a specific connection then copy it out from the old cache to the new one before removing the old cache folder entirely.

The other problem about CoreUI is something that is new in 10.15. I also see that and will investigate what's wrong there. However, this does not hinder the successful execution of Workbench on my machine.

Hi Mike.

I appreciate your attempts to help.

Unfortunately, renaming the cache folder did not fix the issue. I also checked the Console log and the same errors and faults are being thrown.

James

All related files to Workbench that were deleted

Attachment: Screen Shot 2019-11-25 at 1.34.33 PM.png (image/png, text), 146.56 KiB.

I was experiencing the same issue but after uninstalling and reinstalling using AppCleaner the problem resolved. See above comment and link for the files deleted.

Jessica, thanks for your assistance. Unfortunately, deleting with AppCleaner didn't solve the problem. However, I also went ahead and deleted the MySQL folder under ~/Library/Application Support/ (I wonder why AppCleaner didn't delete this folder?) and this seems to have fixed the issue... at least for now. Of course, I need to recreate all my connections, and I lost a bunch of queries, but I guess that's the price I have to pay to have a properly functioning Workbench.

I'm having this same problem after upgrading to catalina, but I just removed the MySQL folder from Application Support as suggested however if you keep your connections.xml you won't lose your connections and you can still get your results grid working agian.