GNOME Bugzilla – Bug 661058
Critical warnings in GtkTreeViewAccessible when removing all columns.
Last modified: 2011-11-16 03:44:10 UTC
Created attachment 198414 [details] Small test case. Steps to reproduce: 1. Compile the given code (see comments at its beginning for quick copy paste commands). 2. Run it in terminal (I had it not maximized, so I could see both terminal and my application not overlapping). 3. When window shows up, press on "5", then on "3". 4. Focus the terminal. 5. Press on "7" and then on "5". 6. Quit test application by clicking the cross in the corner. Expected result: Application prints nothing on console. Actual result: (test:4400): Gtk-CRITICAL **: gtk_tree_view_get_cell_area: assertion `column == NULL || GTK_IS_TREE_VIEW_COLUMN (column)' failed (test:4400): Gtk-CRITICAL **: gtk_tree_view_get_cell_area: assertion `column == NULL || GTK_IS_TREE_VIEW_COLUMN (column)' failed If you are using gnome-shell, you could hit the activities corner twice between points 3. and 4. and receive not two critical warnings but three. This seems to be very reproducible. There is only one thing that _may_ be unusual in this application - removing of all columns from first to last one in tree view in delete-event signal handler (line 86 in code). Warnings do not show up when columns are removed in reverse order.
(In reply to comment #0) > There is only one thing that _may_ be unusual in this application - removing of > all columns from first to last one in tree view in delete-event signal handler > (line 86 in code). And this is something that gtkmm does, so this bug does cause real problems. CCing Benjamin Otte, because Mathias Clasen says that he is spending time fixing problems in this code in GTK+.
I can't reproduce this with GTK master, neither with accessibility enabled nor disabled. Can you get a backtrace from those warnings?
(In reply to comment #2) > I can't reproduce this with GTK master, neither with accessibility enabled nor > disabled. I hope you compiled it with -DSHOW_WARN - this is mentioned at the beginning of the source code. I haven't written about it in my bug report, sorry. > Can you get a backtrace from those warnings? This is backtrack from test application with gtk master.
+ Trace 228739
Also, shiny new procedure to get 4 warnings (my personal record): 1. Compile the given code (see comments at its beginning for quick copy paste commands). 2. Run it in terminal (I had it not maximized, so I could see both terminal and my application not overlapping). 3. When window shows up, focus the terminal. 4. Press on "5", then on "3". 5. Bump the Gnome Shell "Activities" corner twice. 6. Focus the terminal. 7. Press on "7" and then on "5". 8. Quit test application by clicking the cross in the corner.
Benjamin, may we push this?
Push what exactly? I haven't seen a patch in this bug report?
Oh, sorry, I thought we had a patch. Krzesimir, maybe you can try fixing this when you have a moment away from more urgent stuff.
So, I still wasn't able to reproduce it, but I think I know the problem and it should be fixed with the recent treeview accessible refactorings that I pushed to master. I'm going to close this bug for now. If it still happens, please reopen and attack a new backtrace. Thanks.