Dota 2 Crashes With EXC_BAD_ACCESS (SIGSEGV) After Game ...

Home » Code Type X86-64 (translated) » Dota 2 Crashes With EXC_BAD_ACCESS (SIGSEGV) After Game ...

Maybe your like

Skip to content Dismiss alert {{ message }} / Dota-2 Public
  • Notifications You must be signed in to change notification settings
  • Fork 37
  • Star 488
  • Code
  • Issues 644
  • Pull requests
  • Security

    Uh oh!

    There was an error while loading. Please reload this page.

  • Insights
Additional navigation options Dota 2 crashes with EXC_BAD_ACCESS (SIGSEGV) after game starts (post hero selection) #2037New issueNew issueClosedClosedDota 2 crashes with EXC_BAD_ACCESS (SIGSEGV) after game starts (post hero selection)#2037@cvlvxi

Description

@cvlvxicvlvxiopened on Mar 27, 2022

Your system information

  • System information from steam (Steam -> Help -> System Information) in a gist:
M1 Studio Ultra 64GB Ram OSX Monterey 12.3 (up to date)
  • Have you checked for system updates?: [Yes/No] Yes
  • Are you using the latest stable video driver available for your system? [Yes/No] Yes
  • Have you verified the game files?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large pastes as a Github Gist.

Steps for reproducing this issue:

  1. Enter dota. Note same error happens with -vulkan or -gl
  2. Create custom lobby
  3. Select Hero
  4. Enter game after a few seconds (roughly 10seconds) game will crash
------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: dota2 [14715] Path: /Volumes/VOLUME/*/dota2.app/Contents/MacOS/dota2 Identifier: com.valvesoftware.dota2 Version: 1.0.0 Code Type: X86-64 (Translated) Parent Process: bash [14712] Responsible: steam_osx [615] User ID: 501 Date/Time: 2022-03-27 14:56:11.1885 +1100 OS Version: macOS 12.3 (21E230) Report Version: 12 Anonymous UUID: EB87C167-D660-46A0-B663-02C1120987A0 Time Awake Since Boot: 4800 seconds System Integrity Protection: enabled Crashed Thread: 13 GlobPool/10 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0xff807fb1957e3a1c -> 0xffffffb1957e3a1c (possible pointer authentication failure) Exception Codes: 0x0000000000000001, 0xff807fb1957e3a1c Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [14715] VM Region Info: 0xffffffb1957e3a1c is not in any region. Bytes after previous region: 18446603017219668509 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL mapped file 7ffbae4e8000-7ffbdb774000 [722.5M] r-x/r-x SM=COW ...t_id=2b62067d ---> UNUSED SPACE AT END

Can add full problem report if needed

Metadata

Metadata

Assignees

No one assigned

Labels

No labelsNo labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

You can’t perform that action at this time.

Tag » Code Type X86-64 (translated)