Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash at LogManagerImpl #1303

Open
jpalmaduran opened this issue Sep 25, 2024 · 0 comments
Open

Crash at LogManagerImpl #1303

jpalmaduran opened this issue Sep 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jpalmaduran
Copy link

Describe your environment.
SDK: 3.8.32.1
Platform: Windows
OS Version: 10.0.19045.4894
Build String : 10.0.19041.4894 (vb_release.191206-1406)
Build Stamp : 191206-1406
Build Flavor : Free
Build Day : 12/06/2019
OS Version : 10.0.19045.4894
LCID : Portuguese (Brazil)

Steps to reproduce.

We are getting random crashes the updater process. It is not reliable.

What is the expected behavior?
Not a crash.

What is the actual behavior?
A crash

Additional context.
This has started to happen since a couple weeks.

The StackTrace is as follows:

KERNELBASE!RaiseException |   | 0x0000000000000069 |   |   |   | xcpt.c |   | 938
1 | VCRUNTIME140!_CxxThrowException |   | 0x0000000000000090 |   |   |   | throw.cpp |   | 75
2 | ms_teamsupdate!__scrt_throw_std_bad_alloc |   | 0x000000000000001F |   |   |   | throw_bad_alloc.cpp |   | 35
3 | ms_teamsupdate!operator new |   | 0x0000000000000035 |   |   |   | new_scalar.cpp |   | 48
4 | ms_teamsupdate!Microsoft::Applications::Events::LogManagerImpl::LogManagerImpl |   | 0x0000000000001325 |   |   |   | LogManagerImpl.cpp |   | 330
5 | ms_teamsupdate!Microsoft::Applications::Events::LogManagerImpl::LogManagerImpl |   | 0x0000000000000011 |   |   |   | LogManagerImpl.cpp |   | 158
6 | ms_teamsupdate!Microsoft::Applications::Events::LogManagerFactory::Create |   | 0x000000000000004B |   |   |   | LogManagerFactory.cpp |   | 36
7 | ms_teamsupdate!Microsoft::Applications::Events::LogManagerFactory::lease |   | 0x00000000000000F0 |   |   |   | LogManagerFactory.cpp |   | 124
8 | ms_teamsupdate!Microsoft::Applications::Events::LogManagerProvider::Get |   | 0x0000000000000020 |   |   |   | LogManagerProvider.cpp |   | 17
KERNELBASE!RaiseException 0x0000000000000069 xcpt.c 938
1 VCRUNTIME140!_CxxThrowException 0x0000000000000090 throw.cpp 75
2 ms_teamsupdate!__scrt_throw_std_bad_alloc 0x000000000000001F throw_bad_alloc.cpp 35
3 ms_teamsupdate!operator new 0x0000000000000035 new_scalar.cpp 48
4 ms_teamsupdate!Microsoft::Applications::Events::LogManagerImpl::LogManagerImpl 0x0000000000001325 LogManagerImpl.cpp 330
5 ms_teamsupdate!Microsoft::Applications::Events::LogManagerImpl::LogManagerImpl 0x0000000000000011 LogManagerImpl.cpp 158
6 ms_teamsupdate!Microsoft::Applications::Events::LogManagerFactory::Create 0x000000000000004B LogManagerFactory.cpp 36
7 ms_teamsupdate!Microsoft::Applications::Events::LogManagerFactory::lease 0x00000000000000F0 LogManagerFactory.cpp 124
8 ms_teamsupdate!Microsoft::Applications::Events::LogManagerProvider::Get 0x0000000000000020 LogManagerProvider.cpp 17

image

Considering the line that crashes:

        m_system.reset(new TelemetrySystem(*this, *m_config, *m_offlineStorage, *m_httpClient,

We suspect one problem with the dependencies injected into the TelemetrySystem that leads to a crash. Would you folks have any idea of what could be happening here?

We have not changed anything on this part of our code so we suspect possible changes in the system that is running the application leading to the crashes. We would like to know what could be a possible solution in our end to detect before we launch the telemetry, configuring it to avoid crashes.

@jpalmaduran jpalmaduran added the bug Something isn't working label Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant