點擊「刷新」崩潰phpMyAdmin的

Question

我最近更新我的WAMP從PHP 5.5至5.6安裝和開始有與phpMyAdmin的問題。假設它只是我過時的phpMyAdmin版本，我將它更新到版本4.7.4，但問題依然存在。

的問題是，當我在phpMyAdmin單擊工具欄中的刷新（不是在我的瀏覽器），它會導致phpMyAdmin來完全凍結。這發生在我使用大部分工具欄按鈕或控制檯時。在檢查調試器之後，它看起來好像從服務器沒有發送任何響應。我可以點擊列標題以正常順序排列頁面，並且可以進行內聯編輯。

這不會影響我的本地主機上運行的任何其他應用程序。我能夠正常訪問它們並使用它們，但在重新啓動WAMP之前，我無法對phpMyAdmin執行任何操作。

我不是在php_error.log也沒有任何其他的日誌得到任何錯誤。任何想法都可能造成這種情況？

這基本上是我的mysql.log一遍一遍什麼：

2017-08-28 04:05:52 11128 [Note] Plugin 'FEDERATED' is disabled. 
2017-08-28 04:05:52 11128 [Note] InnoDB: Using atomics to ref count buffer pool pages 
2017-08-28 04:05:52 11128 [Note] InnoDB: The InnoDB memory heap is disabled 
2017-08-28 04:05:52 11128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 
2017-08-28 04:05:52 11128 [Note] InnoDB: Compressed tables use zlib 1.2.3 
2017-08-28 04:05:52 11128 [Note] InnoDB: Not using CPU crc32 instructions 
2017-08-28 04:05:52 11128 [Note] InnoDB: Initializing buffer pool, size = 128.0M 
2017-08-28 04:05:52 11128 [Note] InnoDB: Completed initialization of buffer pool 
2017-08-28 04:05:52 11128 [Note] InnoDB: Highest supported file format is Barracuda. 
2017-08-28 04:05:52 11128 [Note] InnoDB: 128 rollback segment(s) are active. 
2017-08-28 04:05:52 11128 [Note] InnoDB: Waiting for purge to start 
2017-08-28 04:05:52 11128 [Note] InnoDB: 5.6.17 started; log sequence number 7435516915 
2017-08-28 04:05:53 11128 [Note] Server hostname (bind-address): '*'; port: 3306 
2017-08-28 04:05:53 11128 [Note] IPv6 is available. 
2017-08-28 04:05:53 11128 [Note] - '::' resolves to '::'; 
2017-08-28 04:05:53 11128 [Note] Server socket created on IP: '::'. 
2017-08-28 04:05:53 11128 [Note] Event Scheduler: Loaded 0 events 
2017-08-28 04:05:53 11128 [Note] wampmysqld64: ready for connections. 
Version: '5.6.17-log' socket: '' port: 3306 MySQL Community Server (GPL) 
2017-08-28 04:08:03 11128 [Note] wampmysqld64: Arrêt normal du serveur 

2017-08-28 04:08:03 11128 [Note] Giving 0 client threads a chance to die gracefully 
2017-08-28 04:08:03 11128 [Note] Event Scheduler: Purging the queue. 0 events 
2017-08-28 04:08:03 11128 [Note] Shutting down slave threads 
2017-08-28 04:08:03 11128 [Note] Forcefully disconnecting 0 remaining clients 
2017-08-28 04:08:03 11128 [Note] Binlog end 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'partition' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_SYS_FIELDS' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_SYS_INDEXES' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_SYS_TABLES' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_FT_CONFIG' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_FT_DELETED' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_METRICS' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_CMPMEM' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_CMP_RESET' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_CMP' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_LOCK_WAITS' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_LOCKS' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'INNODB_TRX' 
2017-08-28 04:08:03 11128 [Note] Shutting down plugin 'InnoDB' 
2017-08-28 04:08:03 11128 [Note] InnoDB: FTS optimize thread exiting. 
2017-08-28 04:08:03 11128 [Note] InnoDB: Starting shutdown... 
2017-08-28 04:08:04 11128 [Note] InnoDB: Shutdown completed; log sequence number 7435516941 
2017-08-28 04:08:04 11128 [Note] Shutting down plugin 'BLACKHOLE' 
2017-08-28 04:08:04 11128 [Note] Shutting down plugin 'ARCHIVE' 
2017-08-28 04:08:04 11128 [Note] Shutting down plugin 'MRG_MYISAM' 
2017-08-28 04:08:04 11128 [Note] Shutting down plugin 'MyISAM' 
2017-08-28 04:08:04 11128 [Note] Shutting down plugin 'MEMORY' 
2017-08-28 04:08:04 11128 [Note] Shutting down plugin 'CSV' 
2017-08-28 04:08:04 11128 [Note] Shutting down plugin 'sha256_password' 
2017-08-28 04:08:04 11128 [Note] Shutting down plugin 'mysql_old_password' 
2017-08-28 04:08:04 11128 [Note] Shutting down plugin 'mysql_native_password' 
2017-08-28 04:08:04 11128 [Note] Shutting down plugin 'binlog' 
2017-08-28 04:08:04 11128 [Note] wampmysqld64: Arrêt du serveur terminé 

在控制檯做一個查詢後，我檢查了網絡選項卡查看請求。這是他們的樣子：

全部都是空白，保存顯示觸發請求的JavaScript堆棧跟蹤。

Answer 1

這種情況可能發生，因爲你使用了XDebug或另一個調試。

PHPMyAdmin是一個PHP應用程序，如果您配置了XDebug，它可以獲取每個PHP執行並在第一行停止 - 它也會觸發PHPMyAdmin。它會一直等到您按下「繼續」或重新啓動服務器。

正如所討論的here，嘗試禁用 「remote_autostart」 和 「profiler_enable」 模式：

xdebug.remote_autostart = 0 
xdebug.profiler_enable = 0 

甚至註釋掉在啓用了XDebug行，如果上面沒有幫助：

;zend_extension = "/absolute/path/to/your/xdebug-extension.so" 

Answer 2

嘗試在config.inc.php文件中將$ cfg ['OBGzip']指令設置爲false，並在您的php配置文件中將zlib.output_compression指令設置爲Off。

來源：https://docs.phpmyadmin.net/en/latest/faq.html

如果沒有，嘗試按照該網頁的故障排除步驟。

希望它有幫助。