How to Quickly Crash RSSOwl with a Large Feed Set

Ron Todd
  • Ron Todd
    Ron Todd

    I’ve been trying, without success, to get RSSOwl to function properly (not crash) when it is subscribed to over 2000 news feeds. When it fails, I generally see an “” error, followed by many “java.lang.NullPointerException”. To help get to the bottom of this, I’ve generated a simple test case, using a small subset of the feeds that Julien Genestoux at Superfeedr put together ( ). My hope is that someone familiar with the internals of RSSOwl will be able to replicate this problem, troubleshoot it, and fix it. Many thanks in advance.

    • This problem appears quickly (generally within a minute) if one cancels out of the initial RSSOwl “Welcome” screen and imports a large OPML file from File -> Import
    • It appears slowly (perhaps in 15 minutes) if one uses the procedure below; or if one imports the same set of feeds from the “Welcome” window
    • One has to be cautious about keeping the periodic update (defaulted to 30 minute intervals) from beginning before the new feeds have completed their first update (genodeftest, on 2013-04-30, diagnosed that there will be a memory leak if new worker threads are spawned before their counterparts have exited)

    (Slow) procedure to replicate failure on large number of feeds (paths assume one is running under Windows)

    1. Set memory allocation to 1024 MB
      a. Take ownership of “Program Files (x86)\RSSOwl\RSSOwl.ini”
      b. Set your permissions to “Full Control”
      c. Edit line 3 to say “-Xmx1024m”, and save
    2. Start RSSOwl on a fresh folder
      a. I invoked through a desktop shortcut with this Target:
      "C:\Program Files (x86)\RSSOwl\RSSOwl.exe" -data D:\RSSOwl\Test\
      b. On the Welcome screen, select “Do not Import Feeds”
      c. Finish
      d. Finish
      e. Tools -> Preferences -> Feeds -> Automatically update the feeds every -> 30 DAYS (effectively turning updates off)
      f. OK
      g. File -> Import -> Import Feeds from a file or Website > Set path to:
      h. Next
      i. Finish
    3. Observe the size of the log file (it is in the data directory specified in step 2.a; as the “.log” file under “.metadata”)
      a. It should start at 1k
      b. When it starts growing rapidly, examine it. I get an “ “ (see below), which is followed by a plethora of “java.lang.NullPointerException”
      c. The application is now hosed (but usually will restart OK and run for a time before crashing again)

    !ENTRY org.rssowl.core 4 2 2013-07-24 11:39:11.917
    !MESSAGE Problems occurred when invoking code from plug-in: "org.rssowl.core".
    !STACK 0
    org.rssowl.core.persist.service.PersistenceException: failed to delete D:\RSSOwl\Test.metadata.plugins\org.rssowl.core\lucene-d786ca1adfc767698acd01135e9e65ad-n-write.lock
    at org.rssowl.core.internal.ApplicationServiceImpl.updateStateOfUnsavedNewNews(
    at org.rssowl.core.internal.ApplicationServiceImpl.access$4(
    at org.rssowl.core.internal.ApplicationServiceImpl$
    at Source)
    at org.rssowl.core.internal.ApplicationServiceImpl.handleFeedReload(
    at org.rssowl.ui.internal.Controller$
    at org.rssowl.core.util.JobQueue$2$
    at Source)
    at org.rssowl.core.util.JobQueue$
    at Source)
    Caused by: failed to delete D:\RSSOwl\Test.metadata.plugins\org.rssowl.core\lucene-d786ca1adfc767698acd01135e9e65ad-n-write.lock
    at org.apache.lucene.index.IndexWriter.closeInternal(
    at org.apache.lucene.index.IndexWriter.close(
    at org.apache.lucene.index.IndexWriter.close(
    ... 13 more

  • sg2002


    Your problem is possibly memory related. 32 bit java is a bit limited with the amount memory it could use - 1GB is usually pushing it.

    Try building 64 bit version of RSSOwl yourself, of try the build I posted here: