search

opentok / opentok-windows-sdk-samples

Sample applications illustrating best practices using OpenTok Windows SDK
MIT License
9 stars 29 forks source link

Periodic error popup and application crash #56

Closed wesoos closed 1 year ago

wesoos commented 1 year ago

Hello, we are intermittently receiving windows error popups in our application. The popup mentions memory, but unfortunately I haven't been able to grab a screen shot of it, and we don't have anything in our own logs. Below is what we get in event viewer.

Faulting application name: TEKControlAllBox.exe, version: 4.0.7.0, time stamp: 0x641de100 Faulting module name: opentok.DLL, version: 2.25.1.0, time stamp: 0x645d8619 Exception code: 0xc0000005 Fault offset: 0x000000000006062d Faulting process id: 0x2ac4 Faulting application start time: 0x01d99a560cdcf6fe Faulting application path: C:\TEKWave Solutions\TEKControl AllBox\TEKControlAllBox.exe Faulting module path: C:\TEKWave Solutions\TEKControl AllBox\opentok.DLL Report Id: 21f14154-f218-4cfb-8f41-24345f1631e5 Faulting package full name: Faulting package-relative application ID:

wesoos commented 1 year ago

Screenshot_3

Attached is a screenshot of the popup

wesoos commented 1 year ago

I reproduced it pretty quickly. I started a video call, ended it, started it again within a few seconds, and got the error...

wesoos commented 1 year ago

Hello, any ideas here?

wesoos commented 1 year ago

Hello, after doing some more debugging and with added logging, it seems this happens in the Session.Dispose() method.

Any updates? This is a major issue...

Thanks

v-kpheng commented 1 year ago

@wesoos, thanks for letting us know about this issue.

Windows SDK 2.25.2 was released recently. Are you able to reproduce on that version as well? Also, are you able to reproduce the issue on our sample apps? If you can reproduce with the sample apps, that will help tremendously.

wesoos commented 1 year ago

Hello, yes I'm using the latest version and having the same issue.

I will have to try and see if I can reproduce with samples. But I'm fairly certain the issue is when disposing the Session object. There is either a memory leak or memory is being accessed incorrectly...

wesoos commented 1 year ago

Hello,

Attached is your sample apps. I have modified the BasicVideoChat app slightly with somewhat of what I'm doing, especially when closing the window. I haven't technically reproduced it while running outside of debugger, but did get an access violation while debugging once and the app crashed. I test by opening the video window and closing constantly.

Thanks opentok-windows-sdk-samples-main.zip

wesoos commented 1 year ago

Are there any debug logging I can turn on?

v-kpheng commented 1 year ago

Thanks, @wesoos, for the sample app. We tried to reproduce the crash but aren't able to. I think we might be missing some nuance, though. Any ideas?

wesoos commented 1 year ago

I'm not sure what else to do. My application is much bigger than the sample app, but the crash is happening in the Session.Dispose(). Is there any logging we can turn on, or can you add any logging that would help diagnose what's happening, and I'll help troubleshoot...

wesoos commented 1 year ago

Hello, any updates?

wesoos commented 1 year ago

Hello, any updates?

wesoos commented 1 year ago

Hi, we really need to get this resolved. I have nothing to go on because the error is happening in your library, and nothing is being logged. Any update?

wesoos commented 1 year ago

Hello, any update?

wesoos commented 1 year ago

Any update on this?

wesoos commented 1 year ago

Hello, I need to know if this is being addressed and what the status is? I am a paying customer and this library is crashing my application. I am willing to help where I can, but there are no logs to look at.

Please respond as soon as possible..

Thanks

v-kpheng commented 1 year ago

Hello, I need to know if this is being addressed and what the status is? I am a paying customer and this library is crashing my application. I am willing to help where I can, but there are no logs to look at.

Please respond as soon as possible..

Thanks

@wesoos, sorry, I was on vacation. Let me ask engineering.

wesoos commented 1 year ago

@v-kpheng Thanks. Any update?

v-kpheng commented 1 year ago

@v-kpheng Thanks. Any update?

@wesoos, I spoke with engineering. There's some improvements in the upcoming 2.26.0 that may help. ETA for that is in late August.

wesoos commented 1 year ago

Hello, can I get an update on the ETA?

v-kpheng commented 1 year ago

@wesoos, it's fluid. We're still aiming for mid-August, but it may slip to late August.

wesoos commented 1 year ago

Hello, checking in on this update...

wesoos commented 1 year ago

I see there is a pre-release for 2.26.0-release

Can you please let me know what was fixed in it for this issue?

v-kpheng commented 1 year ago

@wesoos, Windows SDK 2.26.0 was released last week. Please let me know if the issue persists. Thanks!

wesoos commented 1 year ago

@v-kpheng Thank you. Can you please let me know what particularly was fixed as it relates to this issue?

wesoos commented 1 year ago

Hello, this issue still persists. I have enable debug logging. Please see attached and advise... Log-Debug20230822.zip

v-kpheng commented 1 year ago

@wesoos, since you filed this same issue with our Support team, let's move the conversation there, please. I'll close this ticket.