
So I tried all the different screen scales available.
Gfxcardstatus 2.1 mac#
That made me think: could this have something to do with the pixel doubling on mac retina screens? (see ). > 0x7fffd6bc4dda : jae 0x7fffd6bc4de4 Ġx7fffd6bc4ddf : jmp 0x7fffd6bbdd6f cerror_nocancel * thread #1: tid = 0xecf7c, 0x00007fffd6bc4dda libsystem_kernel.dylib`_pthread_kill + 10, queue = '-thread', stop reason = signal SIGABRTįrame #0: 0x00007fffd6bc4dda libsystem_kernel.dylib`_pthread_kill + 10 *** set a breakpoint in malloc_error_break to debug Soffice(28014,0x7fffdf7993c0) malloc: *** error for object 0x1110c3c00: incorrect checksum for freed object - object was probably modified after being freed. Process 28014 launched: '/Applications/LibreOfficeDev.app/Contents/MacOS/soffice' (x86_64)

Warn::28001:1:sal/osl/unx/pipe.cxx:395: shutdown() failed: Socket is not connected Process 28001 launched: '/Applications/LibreOfficeDev.app/Contents/MacOS/soffice' (x86_64) (lldb) target create "/Applications/LibreOfficeDev.app/"Ĭurrent executable set to '/Applications/LibreOfficeDev.app/' (x86_64). Master~_07.02.24_LibreOfficeDev_5.3.0.0.alpha0_MacOS_x86-64.dmgĮxperienced similar crash when selecting About LibreOffice that I experienced with the current release When the output has stopped appearing on the console, you can copy and paste the whole ouptu into a text file, and then attach that file to this bug report.Īnd you will be asked if you want to quit the running process (assuming that LO is indeed still running). It might take some time to produce output on the screen, so be patient. If you get a message like SIGSEGV or SIGABRT, you could try typing :Īnd pressing enter. If it fails to starts, messages will be displayed on the console output. Wait for lldb to start and initialize the debugging environment, then at the lldb prompt, type :Īnd LibreOffice will try and start. If you do manage to get hold of a recent debug-enabled build for OSX, you can try running it in a lldb debugging session. However, there don't appear to be any debug-enabled builds in any of the Mac machine directories at present, so you are going to be stuck unless you can build LibreOffice yourself from source.
Gfxcardstatus 2.1 code#
This page was generated by GitHub Pages.Hmm, well the usual way would be to find and download a debug-enabled build of master source code tree from here : Requires macOS >= 10.12 gSwitch is maintained by CodySchrank. GPU control with apple is mostly guess work since there isn’t any documentation, so, If anyone finds anything let me know here! Notes However there could be other API’s that could work, I just can’t find any. It appears that apple has removed the necessary API’s from these macbooks on the modern macOS. This could potentially brick your computer LegacyĪt this time it seems like gSwitch will not work on macbooks older than 2011. Ok I lied you technically can but I DO NOT RECOMMEND IT. gSwitch just switches back to the integrated one as fast as it can. However gSwitch cannot prevent your discrete gpu from being accessed by the operating system, and it will be accessed for a short period of time when a process requests the use of it. You can’t, your macbook was designed to use both, but gSwitch can trick it into using the integrated one most of the time. You cannot force integrated only if you have an external display plugged in. You can force integrated only when you have dependent processes but it might crash those processes. If you change to dynamic switching or discrete only any process that was hungry will become dependent.

A hungry process is one that wants to use the discrete gpu but is not allowed because you have set integrated only. What is a dependent process vs a hungry process?Ī dependent process is one that is currently using your discrete gpu.

And since you plugged in the cable I’m assuming you want to use the display. Unfortunately your mac is designed such that in order to use an external display, it has to use the discrete graphics card. Why does the app go back to dynamic switching when a display is plugged in? The current gpu is also reported in the menu. Otherwise, it will just look like a gear.

The gear will have a dot in the middle when the discrete gpu is active. You probably need to allow the application to run in Settings -> Security & Privacy You can also launch it from the terminal and set the desired setting using -integrated, -discrete, and -dynamic. You can also enable notifications for when your gpu changes (off by default) The app is simple to control with integrated only, discrete only, and dynamic switching in the menu.
