98318 - signal BUS (invalid address alignment) under watchmalloc in nsSupportsArray from nsBookmarksService

Status: RESOLVED INCOMPLETE

(SeaMonkey :: Bookmarks & History, defect)

Description

[Calum Mackay]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.3+) Gecko/20010904
BuildID:    2001090410

app crashed whilst running under watchmalloc.

I had several browser windows open on various pages; I wasn't
actively using bookmarks at the time, although did have the
bookmark manager open (albeit iconified).

t@1 (l@1) terminated by signal BUS (invalid address alignment)
(dbx) where                                                                  
current thread: t@1
=>[1] malloc_unlocked(0x38, 0x3b95b3b3, 0xff394000, 0x38, 0x15daa90,
0x3b95b3b3), at 0xff380f10
  [2] malloc(0x34, 0x536888, 0x0, 0xfee4c598, 0x0, 0x0), at 0xff380e64
  [3] __builtin_new(0x34, 0xfdfb92a4, 0x0, 0x44c3d8, 0x4d0730, 0x1), at 0xff1df094
  [4] Create__15nsSupportsArrayP11nsISupportsRC4nsIDPPv(0x80040000, 0xff1f289c,
0xffbee860, 0x1, 0xffbee868, 0xfdfba3f0), at 0xff168c4c
  [5] NS_NewISupportsArray__FPP16nsISupportsArray(0xffbee860, 0x44c3d8,
0x4d0730, 0x1, 0xffbee868, 0xfcfaf428), at 0xff169c14
  [6] GetBookmarkToPing__18nsBookmarksServicePP14nsIRDFResource(0x0, 0xffbee928,
0x3a98, 0x0, 0x0, 0x0), at 0xfcfa6528
  [7] FireTimer__18nsBookmarksServiceP8nsITimerPv(0x404e80, 0x523298,
0xfcfa67d0, 0xa94, 0x4d0, 0xffbee9b8), at 0xfcfa6844
  [8] FireTimeout__10nsTimerGtk(0x404e80, 0x2, 0x2, 0xa7c, 0x4d0, 0xffbeea30),
at 0xfcf62018
  [9] process_timers__FP11nsVoidArray(0x3aa158, 0xfcf73344, 0x159c4b8,
0xff394000, 0x159c3d8, 0x19), at 0xfcf62200
  [10] TimerCallbackFunc__FPv(0x0, 0xfcf62250, 0x13efd0, 0xfee4c598, 0x0, 0x0),
at 0xfcf622e4
  [11] 0xfee27634(0x3a8c50, 0xffbeec30, 0x0, 0x0, 0x1275bc, 0x0), at 0xfee27633
  [12] 0xfee25d08(0x46c, 0x46c, 0x4d0, 0xa7c, 0x4d0, 0xa7c), at 0xfee25d07
  [13] 0xfee265a8(0xfee4c594, 0xfee4c500, 0x4d0, 0xa7c, 0x4d0, 0xa7c), at 0xfee265a7
  [14] g_main_run(0x17fbe0, 0xff09a894, 0x12a610, 0x0, 0x0, 0xfe9b0b6c), at
0xfee26ed0
  [15] gtk_main(0x2c00, 0xfdcb30a4, 0x13a070, 0xfe94f120, 0xfe8c0dd4, 0x0), at
0xfef4b444
  [16] Run__10nsAppShell(0x157f28, 0xfdcb329c, 0x157f28, 0xfe94ee50, 0x0,
0xffe), at 0xfdcb32d4
  [17] Run__17nsAppShellService(0x13c058, 0xfe949688, 0x13c058, 0xfe94a554,
0xffbeed98, 0xff219640), at 0xfe94969c
  [18] 0x188a8(0x0, 0xffbef054, 0x0, 0x5, 0x100d4, 0x0), at 0x188a7
  [19] main(0x0, 0xffbef054, 0xffbef05c, 0x2ed48, 0x0, 0x0), at 0x19318


Reproducible: Couldn't Reproduce

Comment 1

[Keyser Sose]

Marking nEW.

Comment 2

[Ben Goodger (use ben at mozilla dot org for email)]

Paul Chen is now taking Bookmarks bugs. For your convenience, you can filter 
email notifications caused by this by searching for 'ilikegoats'.

Comment 3

[Paul Chen]

Mass move Ben's bugs dumped on me marked future with p5 to get off my untriaged
radar. You can filter out this email by looking for "ironstomachaussie"

Comment 4

[Peter Trudelle]

mass reassign of pchen bookmark bugs to ben

Comment 5

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 7

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 8

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 10

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 12

[Wayne Mery (:wsmwk)]

I don't see that this is worth keeping - several gecko releases old, no symbols, and wasn't able to reproduce per comment 0