Closed Bug 953500 Opened 10 years ago Closed 10 years ago

Exception and crash when starting two Instantbirds

Categories

(Instantbird Graveyard :: Contacts window, defect)

0.1.1
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bugzilla, Assigned: florian)

Details

Attachments

(2 files)

*** Original post on bio 49 at 2008-03-19 20:08:00 UTC ***

When starting Instantbird a second time exception:
[Exception... "Component returned failure code: 0xc1f30002 (NS_ERROR_ALREADY_INITIALIZED) [purpleICoreService.init]"  nsresult: "0xc1f30002 (NS_ERROR_ALREADY_INITIALIZED)"  location: "JS frame :: chrome://instantbird/content/blist.js :: initPurpleCore :: line 210"  data: no]

After that, a second (bugged) buddy list pops up. No contact seems to be in there. At closing time, the whole application segfault and everything is closed (including the first Instantbird).

To have the first buddy list getting focus when trying to start Instantbird a second time would look  lot better...
Hardware: x86 → All
Target Milestone: --- → 0.1.2
Version: trunk → 0.1.1
*** Original post on bio 49 at 2008-04-07 17:13:11 UTC ***

I think this should be fixed as soon as possible... That might not be difficult and would help a lot.
*** Original post on bio 49 as attmnt 25 at 2008-06-22 18:57:00 UTC ***

Let's fix the crash first...
*** Original post on bio 49 at 2008-06-22 18:59:31 UTC ***

Comment on attachment 8351769 [details] [diff] [review] (bio-attmnt 25)
patch for the crash

Envoi          purple/purplexpcom/src/purpleCoreService.cpp
Transmission des donnees .
Revision 213 propagee.
*** Original post on bio 49 as attmnt 26 at 2008-06-22 20:05:00 UTC ***

And now, focus the previous buddy list if there is already one.
*** Original post on bio 49 at 2008-06-22 20:09:05 UTC ***

Envoi          instantbird/base/content/instantbird/blist.js
Envoi          instantbird/base/content/instantbird/blist.xul
Transmission des donnees ..
Revision 214 propagee.

Fixed!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.