Skip to content

Conversation

@Nbc66
Copy link
Contributor

@Nbc66 Nbc66 commented Jun 4, 2025

Description

There is a crash that happens in the neo_loading UI which is caused by m_bInfoLabel being an invalid memory address
This fixes it by just removing the info label step

Toolchain

  • Windows MSVC VS2022
  • Linux GCC Distro Native [Specify distro + GCC version]
  • Linux GCC 10 Sniper 3.0

Linked Issues

  • fixes #
  • related #

{
NeoUI::Label(L"Press ESC to cancel");
if (m_pLabelInfo) NeoUI::Label(m_pLabelInfo->GetTextImage()->GetUText());
if (m_pLabelInfo) //NeoUI::Label(m_pLabelInfo->GetTextImage()->GetUText());
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But this will cause it to if over the next line and no one else seem to have this issue so I wouldnt completely cut it out? You altered the loading dialog UI/res file, localization difference, or something? At most can just expand the if statement to check more pointers.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the thing i would recomend is just get the uText at the beginning when you cast it to a label there is no other way of doing this also I haven't touched a single resfile for this. this only happens cause the pointer becomes invalid after moving out of the scope when casting the pointer and the pointer becoming corupted

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not too sure if the text gets properly updated on each onmessage activate. You could also try to nullptr out the panel pointers on deactivate and just before refetching panels to see if it helps somewhat

@AdamTadeusz
Copy link
Contributor

so it's a problem with the source sdk 2013 mp version, close?

@nullsystem
Copy link
Collaborator

Superseded by #1183

@nullsystem nullsystem closed this Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants