docs » hs.crash

Attempts to reduce RAM usage of Hammerspoon

• None

• None

• This function will print some memory usage numbers (in bytes) to the Hammerspoon Console before and after forcing Lua's garbage collector

Causes Hammerspoon to immediately crash

• None

• None

• This is for testing purposes only, you are extremely unlikely to need this in normal Hammerspoon usage

Sets a key/value pair in any Sentry crash dump generated by this Hammerspoon session

• key - A string containing the key name of the pair
• value - A string containing the value of the pair

• None

Leaves a breadcrumb log message in any Sentry crash dump generated by this Hammerspoon session

• logMessage - A string containing a message to log

• None

• This is probably only useful to extension developers. If you are trying to track down a confusing crash, and you have access to the Sentry project for Hammerspoon (or access to someone who has access!), this can be a useful way to leave breadcrumbs from Lua in the crash dump

Dumps the contents of Lua's CLIBS registry

• None

• A table containing all the paths of C libraries that have been loaded into the Lua runtime

• This is probably only useful to extension developers as a useful way of ensuring that you are loading C libraries from the places you expect.

Gets the resident size of the Hammerspoon process

• None

• An integer containing the amount of RAM in use by Hammerspoon (in bytes), or nil if an error occurred

Causes Hammerspoon to generate an Objective C exception

• name - A string containing the name of the exception
• message - A human readable string explaining the exception

• None

• Outside of a context of a Lua pcall() (or a C lua_pcall()), this will cause Hammerspoon to exit. We follow the safe behaviour of terminating the app on any unhandled Objective C exception.