MacOS Crash after some time

Create issue
Issue #56 new
Former user created an issue

If it runs for a longer time it always ends in an crashs:

[16:50:32] INFO Provider:153 - Checking download directory. Removing some wallpapers if it is necessary... [16:50:35] INFO WallhavenProvider:75 - Downloading wallpaper with keyword -> NONE

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x000000010f9353bf, pid=6133, tid=0x0000000000009c2f

JRE version: Java(TM) SE Runtime Environment (8.0_131-b11) (build 1.8.0_131-b11)

Java VM: Java HotSpot(TM) 64-Bit Server VM (25.131-b11 mixed mode bsd-amd64 compressed oops)

Problematic frame:

C [libawt_lwawt.dylib+0x1c3bf] OGLSD_SetScratchSurface+0x49

Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

An error report file with more information is saved as:


If you would like to submit a bug report, please visit:

The crash happened outside the Java Virtual Machine in native code.

See problematic frame for where to report the bug.

Abort trap: 6

Comments (4)

  1. Eloy García Almadén repo owner

    Hi @Peter Auerbacher and thanks again four your feedback.

    I’ve seen the hs_err log and I cannot figure out what is happening. If the error was produced by any bug in the application, I think it should be displayed in wallpaperdownloader.log. Does this log shows something unusual?

    We can try several things in order to see if the application doesn’t crash. What is the command you are using to run the application? I assume that you are executing WallpaperDownloader directly from command line with the full jar which is in the official repository right?

  2. Peter Auerbacher

    I start it with: java -Dsun.java2d.xrender=f -Xmx512m -Xms256m -jar wallpaperdownloader.jar

  3. Eloy García Almadén repo owner

    Hi again!

    Ok, so you are using all the arguments needed to avoid several issues related to the application. 😞

    Did WallpaperDownloader always failed this way or has it started crashing after some update like Java version, Operating System upgrade…?

  4. Log in to comment