49303 - Method newBookmarkEntry(String string) in Bookmarks interface crashed on null string

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Java APIs to WebShell, defect, P3)

Description

[Vladimir Strigun]

When try to call method newBookmarkEntry(null) Webclient crashed.
Webclient crashed when try to call native method from JDK - 
const char* GetStringUTFChars(jstring str, jboolean *isCopy) 

Expected behaviour:
Code must contain verification for null argument and must thrown a 
NullPointerException exception or java.lang.IllegalArgumentException.

Platform & OS: WinNT 4.0 Webclient sources from 10.08.2000

Comment 1

[Blake Ross]

Adding crash keyword to all open crashers

Comment 2

[buster]

confirming bug based on it being a code-level issue (no reproducable test case
in hand, but needs attention at the code level.)

Comment 3

[geetha.vaidyanaathan]

Adding Status whiteboard keyword to track all Webclient existing bugs

Comment 4

[edburns]

Fix checked in.

Comment 5

[Vladimir Strigun]

This bug still reproduced on Mozilla under NT (Mozilla/5.0 (Windows; U; 
WinNT4.0; en-US; rv:0.9.1) Gecko/20010915).
I cannot found a check for null parameter in function GetStringUTFChars ...

Comment 6

[Henrik Lynggaard Hansen]

This was last checked on  mozilla 0.9.1  (2001-09-17).

Reporter (or someone else) could you please test if the problem is still
present. If so please tell us otherwise close the bug.

Comment 7

[Brant Gurganus]

By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and
<http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss
bugs are of critical or possibly higher severity.  Only changing open bugs to
minimize unnecessary spam.  Keywords to trigger this would be crash, topcrash,
topcrash+, zt4newcrash, dataloss.

Comment 8

[Robert Kaiser]

There hasn't been any activity in here for a very long time and it's very much unclear if this problem still applies in any way to current versions of our products. If it still does and you can reproduce in such a modern version, please attach a link to a crash report from about:crashes when reopening the bug. As it stands now it's not actionable for developers, but a crash report from a current version could make it workable.