search

Aurora-RGB / Aurora

Unified lighting effects across multiple brands and various games. http://www.project-aurora.com/
http://www.project-aurora.com/
MIT License
266 stars 38 forks source link

V153 Pre-Release, Random Crash - Logs included. #160

Closed NeoDaemon closed 1 year ago

NeoDaemon commented 1 year ago
Since updating to v153 Aurora is crashing sometimes, W11, Latest LGHub. Hardware: G512 & G503 ### Expected Behaviour Normal operation ### Actual Behaviour Ramdom crash, can happen at the start of the program or hours later. ### Frequency Daily ### Aurora Version: V153 Pre-Release ### Previously an Issue? No

V153

2023-07-22 06.42.04.log 2023-07-22 08.47.28.log 2023-07-22 21.19.05.log 2023-07-23 06.14.07.log 2023-07-23 20.11.48.log 2023-07-23 20.47.00.log

NeoDaemon commented 1 year ago

V159 crashed too, Testing V160 now. To add to previous data: Program crashes, but doesn't stop working until i accept the error showed before. 2023-07-25 20.55.1120230725.log

Aytackydln commented 1 year ago

Thanks, this is very random for me so will be hard do debug. It should still be present in v160

Sadly logs don't tell me much

xerxes-at commented 1 year ago

I'm using a wireless headset and noticed that this error message always occurs twice when my headset is connected / disconnected while Aurora is running. With that knowledge I took a quick look at the source code and found out that commenting out this line prevents the issue from happening. Which explains why I get the message twice as the headset's microphone and playback device are added / removed. Of course this is no real fix but I hope it give you enough information to check the context in which the code is run.

ShizCalev commented 1 year ago

I get this crash every time my bluetooth earbuds connect / disconnect from my PC.

Aytackydln commented 1 year ago

Thanks all, I think I solved this. Will push next release with fix soon

Aytackydln commented 1 year ago

Please confirm it is fixed: https://github.com/Aurora-RGB/Aurora/releases/tag/v161

xerxes-at commented 1 year ago

Works as expected on my end with v162. Thank you for the quick fix.

NeoDaemon commented 1 year ago

Yeah, v162 was pretty solid yesterday. Thanks for the prompt fix! But my bug wasn't triggered by any connect/disconnect event, but that fix also worked here. Thanks again!