[GH-ISSUE #3449] inspect-managed-members: resource-limit on valid 2.2 MB managed PE (HP OMEN Gaming Hub) while smaller peers parse fully #1292

New issue

Closed

opened 2026-10-16 21:03:50 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-16 21:03:50 +00:00

Owner

Originally created by @tomyrms on GitHub (Oct 14, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/3449

Summary

rea inspect-managed-members fails with a resource-limit on two .NET assemblies shipped with HP OMEN Gaming Hub, while other assemblies from the same package are analyzed completely (including one whose member dump is ~4.5 MB of JSON).

Environment: Windows 11 x64, rea-agents 6.4.0 (npm global), Node 26.8.1, managed static provider only (no Ghidra/IDA configured).

Repro

rea inspect-managed-members "C:\Program Files\WindowsApps\AD2F1837.OMENCommandCenter_1101.2609.11.0_x64__v10z8vjag6ke6\OmenCommandCenterApp\HP.Omen.Core.Common.dll" --format json

Excerpt of the result:

"metadata": { "status": "partial", "version": null, "table_row_counts": {} },
"coverage": { "state": "unavailable", "issues": [ { "code": "resource-limit", "scope": "metadata.representation", "offset": 938934, "detail": "Managed metadata exceeds the 67108864 byte representation budget" } ] },
"limitations": [ "The CLI metadata could not be admitted; managed member inspection is unavailable." ]

Second failing file:

rea inspect-managed-members "...\OmenCommandCenterApp\HP.Omen.Core.Model.Device.dll" --format json

→ same resource-limit issue (offset: null).

Artifact facts (no files attached: proprietary HP software)

File	SHA-256	Size
HP.Omen.Core.Common.dll	`f55f3c163fbec467a86fe8c0d7eed9c3dbd59e9d06d4be137b5014ac1cde20ef`	2,218,504 bytes
HP.Omen.Core.Model.Device.dll	`0d5ea2003bd46a02f50ab6ec821579984651fcd5e0b2dfc994c02c12b34cfdf1`	489,992 bytes

Both are ordinary PE x86_64 managed assemblies that load and decompile correctly in other tooling.

Observations

rea inspect-managed-artifact succeeds on the same files (custom attribute rows are enumerated).
Assemblies from the same directory parse completely, e.g. HP.Omen.Background.PerformanceControl.dll (members + IL anchors + call edges) and HP.Omen.Features.Hardware.PerformanceMonitorBg.dll (737 KB JSON).
A 2.2 MB file exceeding a 64 MiB "representation budget" suggests the budget is applied to an expanded representation (e.g. heap-size heuristics), and a large #Blob/#CustomAttribute stream may be tripping it.
I could not find a documented flag or environment variable to raise the budget; resource-limit on metadata.representation is not described in the docs I could find.

Impact

Member-level static analysis is unavailable for the central assemblies of this software (the HSA/WMI client layer), which is where the managed provider is most valuable.

Happy to re-run against any test build and to produce further diagnostics (e.g. exact heap sizes) if that helps narrow this down.

Originally created by @tomyrms on GitHub (Oct 14, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/3449 ## Summary `rea inspect-managed-members` fails with a `resource-limit` on two .NET assemblies shipped with HP OMEN Gaming Hub, while other assemblies from the same package are analyzed completely (including one whose member dump is ~4.5 MB of JSON). Environment: Windows 11 x64, rea-agents 6.4.0 (npm global), Node 26.8.1, managed static provider only (no Ghidra/IDA configured). ## Repro ``` rea inspect-managed-members "C:\Program Files\WindowsApps\AD2F1837.OMENCommandCenter_1101.2609.11.0_x64__v10z8vjag6ke6\OmenCommandCenterApp\HP.Omen.Core.Common.dll" --format json ``` Excerpt of the result: ```json "metadata": { "status": "partial", "version": null, "table_row_counts": {} }, "coverage": { "state": "unavailable", "issues": [ { "code": "resource-limit", "scope": "metadata.representation", "offset": 938934, "detail": "Managed metadata exceeds the 67108864 byte representation budget" } ] }, "limitations": [ "The CLI metadata could not be admitted; managed member inspection is unavailable." ] ``` Second failing file: ``` rea inspect-managed-members "...\OmenCommandCenterApp\HP.Omen.Core.Model.Device.dll" --format json ``` → same `resource-limit` issue (`offset: null`). ## Artifact facts (no files attached: proprietary HP software) | File | SHA-256 | Size | |---|---|---| | HP.Omen.Core.Common.dll | `f55f3c163fbec467a86fe8c0d7eed9c3dbd59e9d06d4be137b5014ac1cde20ef` | 2,218,504 bytes | | HP.Omen.Core.Model.Device.dll | `0d5ea2003bd46a02f50ab6ec821579984651fcd5e0b2dfc994c02c12b34cfdf1` | 489,992 bytes | Both are ordinary PE x86_64 managed assemblies that load and decompile correctly in other tooling. ## Observations - `rea inspect-managed-artifact` succeeds on the same files (custom attribute rows are enumerated). - Assemblies from the same directory parse completely, e.g. `HP.Omen.Background.PerformanceControl.dll` (members + IL anchors + call edges) and `HP.Omen.Features.Hardware.PerformanceMonitorBg.dll` (737 KB JSON). - A 2.2 MB file exceeding a 64 MiB "representation budget" suggests the budget is applied to an expanded representation (e.g. heap-size heuristics), and a large `#Blob`/`#CustomAttribute` stream may be tripping it. - I could not find a documented flag or environment variable to raise the budget; `resource-limit` on `metadata.representation` is not described in the docs I could find. ## Impact Member-level static analysis is unavailable for the central assemblies of this software (the HSA/WMI client layer), which is where the managed provider is most valuable. Happy to re-run against any test build and to produce further diagnostics (e.g. exact heap sizes) if that helps narrow this down.

bsakaguchi referenced this issue

2026-10-17 21:01:32 +00:00

[GH-ISSUE #2383] [Tracker] Audit analysis and debugging coverage for the TIOBE top 100 languages (October 2026) #794

bsakaguchi closed this issue

2026-10-17 21:01:51 +00:00

bsakaguchi referenced this issue

2026-10-17 21:10:04 +00:00

[PR #1292] [MERGED] fix(javascript): preserve uncertainty after references escape to calls #2772

bsakaguchi referenced this issue

2026-10-17 21:10:04 +00:00

[PR #1294] [MERGED] test(process): check malformed capture choices concurrently #2774

bsakaguchi referenced this issue