Title: TLloancy Stack Trace
Author: Thomas Lloancy
Published: <strong>2026年9月15日</strong>
Last modified: 2026年9月15日

---

プラグインを検索

![](https://ps.w.org/tlloancy-stack-trace/assets/banner-772x250.png?rev=3696705)

![](https://ps.w.org/tlloancy-stack-trace/assets/icon-256x256.png?rev=3696705)

# TLloancy Stack Trace

 作者: [Thomas Lloancy](https://profiles.wordpress.org/tlloancy/)

[ダウンロード](https://downloads.wordpress.org/plugin/tlloancy-stack-trace.1.0.0.zip)

 * [詳細](https://ja.wordpress.org/plugins/tlloancy-stack-trace/#description)
 * [レビュー](https://ja.wordpress.org/plugins/tlloancy-stack-trace/#reviews)
 *  [インストール](https://ja.wordpress.org/plugins/tlloancy-stack-trace/#installation)
 * [開発](https://ja.wordpress.org/plugins/tlloancy-stack-trace/#developers)

 [サポート](https://wordpress.org/support/plugin/tlloancy-stack-trace/)

## 説明

TLloancy Stack Trace records PHP fatals (memory exhausted, parse error, and similar),
uncaught exceptions, `wp_die` failures, and exceptions that a third-party plugin
caught so the site would not white-screen.

Each row stores:

 * The last SQL that actually belongs to the crash (from `$wpdb`, or from a small
   adapter when a plugin talks to MySQL outside `$wpdb`)
 * Memory usage, peak, and the configured limit
 * File and line
 * The plugin, theme, or core component most likely involved
 * The request URL

Entries live in a dedicated table, under Tools  Stack Trace. You can export CSV 
or clear the log.

This is not a debug.log viewer and not a live profiler. Generic log plugins tail
PHP or WordPress logs. Stack Trace records **why a request died**: the SQL that 
belongs to the crash (including plugins that never set `$wpdb->last_query`), memory
at the limit, and exceptions another plugin caught so the site would not white-screen.
Typical case: an All-in-One WP Migration export that fails with “refresh and try
again” while the real cause is a 128M SELECT or a full disk.

It is for the morning after: the site crashed, nobody was watching, and you want
the cause.

#### Plugins that bypass $wpdb

Some exporters (All-in-One WP Migration among them) run SQL on `$wpdb->dbh` directly.`
$wpdb->last_query` is then empty or already overwritten (cron, Action Scheduler).
Stack Trace keeps SQL in memory via adapters and, on failure, can read that plugin’s
own error-log `last_query` field. It does not edit third-party files and does not
hook their export pipeline as a stage.

#### Automatic update failure emails (WordPress 7.2+)

A failed automatic plugin update already includes the fatal message, file, and line.
Stack Trace adds memory and last SQL from the same loopback check, with a link to
the full log.

## インストール

 1. Upload the `tlloancy-stack-trace` folder to `/wp-content/plugins/`.
 2. Activate the plugin from the Plugins screen.
 3. Open the log under Tools  Stack Trace.

## FAQ

### Does this slow the site down?

On a normal request the cost is a shutdown callback that returns immediately unless
PHP reports a fatal. A row is written only when something is recorded. Adapters 
add work only for the target plugin’s AJAX (for example an All-in-One export hop):
a header check on success, disk I/O only on failure.

### How many entries are kept?

300 by default. Older rows are pruned when you open the admin page. Override the
limit with `TLLST_MAX_ENTRIES` in wp-config.php.

### Does the plugin change other plugins’ files?

No. It does not reorder `active_plugins` and it does not patch files on disk.

### Why is the last SQL not always from $wpdb?

If the crash is inside a known custom MySQL client, `$wpdb->last_query` is often
unrelated. The adapter’s in-memory SQL (or that plugin’s error log) is used instead.

## 評価

このプラグインにはレビューがありません。

## 貢献者と開発者

TLloancy Stack Trace はオープンソースソフトウェアです。以下の人々がこのプラグイン
に貢献しています。

貢献者

 *   [ Thomas Lloancy ](https://profiles.wordpress.org/tlloancy/)

[“TLloancy Stack Trace” をあなたの言語に翻訳しましょう。](https://translate.wordpress.org/projects/wp-plugins/tlloancy-stack-trace)

### 開発に興味がありますか ?

[コードを閲覧](https://plugins.trac.wordpress.org/browser/tlloancy-stack-trace/)
するか、[SVN リポジトリ](https://plugins.svn.wordpress.org/tlloancy-stack-trace/)
をチェックするか、[開発ログ](https://plugins.trac.wordpress.org/log/tlloancy-stack-trace/)
を [RSS](https://plugins.trac.wordpress.org/log/tlloancy-stack-trace/?limit=100&mode=stop_on_copy&format=rss)
で購読してみてください。

## 変更履歴

#### 1.0.0

 * Initial release.
 * Fatals, swallowed exceptions, and memory crashes with SQL, memory, file/line.
 * Adapter for All-in-One WP Migration (observe only).
 * WordPress 7.2 automatic update failure emails include memory and last SQL from
   the loopback check, per failed plugin.

## メタ

 *  バージョン **1.0.0**
 *  最終更新日 **4週間前**
 *  有効インストール数 **10未満**
 *  WordPress バージョン ** 6.0またはそれ以降 **
 *  検証済み最新バージョン: **7.1.3**
 *  PHP バージョン ** 7.4またはそれ以降 **
 *  言語
 * [English (US)](https://wordpress.org/plugins/tlloancy-stack-trace/)
 * タグ
 * [crash](https://ja.wordpress.org/plugins/tags/crash/)[debug](https://ja.wordpress.org/plugins/tags/debug/)
   [error log](https://ja.wordpress.org/plugins/tags/error-log/)[fatal error](https://ja.wordpress.org/plugins/tags/fatal-error/)
   [memory](https://ja.wordpress.org/plugins/tags/memory/)
 *  [詳細を表示](https://ja.wordpress.org/plugins/tlloancy-stack-trace/advanced/)

## 評価

レビューはまだ送信されていません。

[Your review](https://wordpress.org/support/plugin/tlloancy-stack-trace/reviews/#new-post)

[すべてのレビューを見る](https://wordpress.org/support/plugin/tlloancy-stack-trace/reviews/)

## 貢献者

 *   [ Thomas Lloancy ](https://profiles.wordpress.org/tlloancy/)

## サポート

意見や質問がありますか ?

 [サポートフォーラムを表示](https://wordpress.org/support/plugin/tlloancy-stack-trace/)