Constant OnFrame / Launch.lua Crashes

[0x42424242]

Check version

• I'm running the latest version of Path of Building and I've verified this by checking the changelog

Check for duplicates

• I've checked for duplicate open and closed issues by using the search function of the issue tracker

What platform are you running Path of Building on?

Windows

How is Path of Building expected to behave?

Expecting normal usage / not constant crashes and / or errors.

How does Path of Building behave?

I'm getting constant OnFrame errors with the latest version of PoB. This happens on all screens, including the builds index. A stack trace as an example from the Build index screen.

Error:

In 'OnFrame': Modules/ModParser.lua:6364: calling 'find' on bad self (string expected, got nil)
stack traceback:
	[C]: in function 'find'
	Modules/ModParser.lua:6364: in function 'scan'
	Modules/ModParser.lua:6498: in function 'parseMod'
	Modules/ModParser.lua:6744: in function 'parseMod'
	Classes/Item.lua:743: in function 'ParseRaw'
	Classes/ItemsTab.lua:1036: in function <Classes/ItemsTab.lua:1004>
	Modules/Build.lua:630: in function 'CallMode'
	Modules/Main.lua:354: in function <Modules/Main.lua:340>
	[C]: in function 'PCall'
	Launch.lua:111: in function <Launch.lua:108>
v2.63.0 master
Press Enter/Escape to dismiss, or F5 to restart the application.
Press CTRL + C to copy error text.

A stack trace while viewing the calc tab.

Error:

In 'OnFrame': Classes/CalcSectionControl.lua:291: attempt to index field 'calcsTab' (a trace value)
stack traceback:
	Classes/CalcSectionControl.lua:291: in function 'Draw'
	Classes/ControlHost.lua:91: in function 'DrawControls'
	Classes/CalcsTab.lua:342: in function 'Draw'
	Modules/Build.lua:1204: in function 'CallMode'
	Modules/Main.lua:370: in function <Modules/Main.lua:340>
	[C]: in function 'PCall'
	Launch.lua:111: in function <Launch.lua:108>
v2.63.0 master
Press Enter/Escape to dismiss, or F5 to restart the application.
Press CTRL + C to copy error text.

This is occurring at a fairly constant rate to the point that it's relatively unusable. (Every few seconds, I imagine as part of the UI loop).

I have attempted an uninstall / reinstall but the behaviour / bug has persisted.

How to reproduce the issue

No set behavior appears to trigger this behavior, in that I can't mouse over a particular field and trigger it constantly. It does appear to occur when interacting with the program, navigating around menus, etc.

[Nightblade]

What model CPU do you have?

[0x42424242]

I have a i9-14900K

[Nightblade]

Do you have issues with other apps too?

You might want to try these potential fixes (one at a time):

• Reduce the performance core ratio to 54x
• Set the process affinity of PoB to only use 1 core (23rd core for example)

If neither of those help let us know.

[0x42424242]

Gave a crack with the core affinity but it still crashed directly after trying that. No issues with any other games although I acknowledge the 14900k has had a chequered past. It's also worth saying that I've been a POB user for many years, including on this PC, and the issue has only appeared in the last 1-2 versions (I can't remember precisely the version that started acting up), but I remember distinctly keeping an eye out for updates hoping that it would be fixed with others having the same issue. Turns out, it just might be a rarer bug than I thought if I'm the only one reporting it.

Happy to help with any other diagnostic information that I can.

[Nightblade]

Ok, thanks for trying anyway. Did you try setting the affinity?

[0x42424242]

Hey, I tested the affinity - it was actually the performance core ratio reduction I hadn't tried yet. I've given that a crack now (was hoping not to have to reduce the whole PC performance but oh well).

POB has passed the "nothing has happened for 30 seconds after launching" test, so I'll keep it on for a few hours and report back. If nothing happens I'll post in here and close with a comment.

Appreciate your help / responsiveness.

[Nightblade]

Sorry for my confusion, glad you worked it out 😀