(Update: EXC_BAD_ACCESS Crash doesn't occur on 4.0.0.a1) Trying to solve crash on 4.0.0.a2

This forum is about all development around libVLC.
Eveiw
New Cone
New Cone
Posts: 1
Joined: 22 Apr 2023 02:01

(Update: EXC_BAD_ACCESS Crash doesn't occur on 4.0.0.a1) Trying to solve crash on 4.0.0.a2

Postby Eveiw » 04 May 2023 07:13

Update: The crash does not occur on 4.0.0.a1, which may have to do with how 4.0.0.a2 is handling `media` (In the newer version, I'm required to do `media!` instead of `media` when setting up the player).

(running MacOS Monterey 12.6.5 on a 2019 MacBook Pro)

Hello VLC community,

I've been encountering a EXC_BAD_ACCESS [1] crash when starting to play a video with the latest VLCKit version (4.0.0.a2).

To address the crash, I've decided to try building the framework from a specific user's repository (https://code.videolan.org/umxprime/VLCK ... ts-handler).

It appears I've built VLCKit using the following terminal line:

`./compileAndBuildVLCKit.sh -a x86_64`

The build process generated a lot of output in the terminal and created a new "vlc" folder, but I don't know to use the result in Xcode for my MacOS app. I couldn't find a "VLCKit.framework" or ".xcframework" file.

Thank you for any help!

[1] - If helpful (crash occurs at arrow)l:

'''
0x111036e7f <+63>: movq 0x2ba9b62(%rip), %rsi ; "mediaPlayerLengthChanged:"
0x111036e86 <+70>: callq *0x2abf704(%rip) ; (void *)0x00007ff804e24400: objc_msgSend
-> 0x111036e8c <+76>: movq -0x18(%rbp), %rdi
0x111036e90 <+80>: callq *0x2abf732(%rip) ; (void *)0x00007ff804e27000: objc_release
'''

Return to “Development around libVLC”

Who is online

Users browsing this forum: No registered users and 10 guests