Possible NPE while evaluating java library path

[GoogleCodeExporter]

This issue is an bugfix for JCEF (patch 1 of 10)
------------------------------------------------

What steps will reproduce the problem?
1. Set some kind of java-library path
2. Start jcef MainFrame app

What is the expected output? What do you see instead?
There is a possible NPE while evaluating the java library path.
In some situations "String[] found" can be null because 
dir.list() returns null if the pathname does not denote a directory,
or if an I/O error occurs.

What version of the product are you using? On what operating system?
rev.31

Please provide any additional information below.
Attached you'll find a simple patch file which fixes this problem

Original issue reported on code.google.com by k...@censhare.de on 8 Mar 2014 at 7:52

• Blocking: Refactor JCEF to match CEF structure and functionality #55, Split CefClientDelegate in several handlers to get a more cef-like implementation. #46

Attachments:

• 01_2014-03-03_issue_XX_NPE_while_searching_lib_path.patch

[GoogleCodeExporter]

Original comment by magreenb...@gmail.com on 12 Mar 2014 at 9:50

• Now blocking: Refactor JCEF to match CEF structure and functionality #55

[GoogleCodeExporter]

Original comment by magreenb...@gmail.com on 12 Mar 2014 at 9:51

• Now blocking: Split CefClientDelegate in several handlers to get a more cef-like implementation. #46

[GoogleCodeExporter]

Fixed in revision 32.

Original comment by magreenb...@gmail.com on 28 Mar 2014 at 10:10

• Changed state: Fixed