I know this sounds odd, but every time I save a View on this older site, it in turn triggers menu_router_build somehow (only admin_menu makes a call to this function, 6.x-1.6). This causes the site to blow up and MySQL to quit responding, it's almost like its triggered multiple times in a row. When it finally loads (3 minutes later) the page is filled with duplicate key error entries.

Are these two issues correlated? How can I fix this?

Comments

dawehner’s picture

Currently this is done because changing the path in the menu settings might require rebuilding the menu.

There is though another report about that problem: #941970: Only set router rebuild needed when something related to routing actually changes
Another question: why do you use the views ui on your live enviroment, you should better do this just on development and export your views into code.

kevinquillen’s picture

We also noticed that we get hundreds of duplicate key errors on nearly every page load in the admin- I only noticed it on views. It happens on both dev and production, but the only call to menu_router_build is in admin_menu. I wonder if its been snuck into the db somehow in a php node or block.

dawehner’s picture

It would be interesting to know which table has the duplicate key errors? I guess it's the menu router table, though this is hard to fix as this is part of the menu api.

kevinquillen’s picture

Yeah. menu_router entries. I was working in Views mostly while a coworker was getting it basically everywhere. Trying to pin down what is triggering it.

mustanggb’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)