Bug 510375

Summary:	thunderbird crashes randomly with 'INTERNAL ERROR'
Product:	[Fedora] Fedora	Reporter:	Lonni J Friedman <netllama>
Component:	thunderbird	Assignee:	Gecko Maintainer <gecko-bugs-nobody>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	low
Version:	11	CC:	gecko-bugs-nobody, mcepl
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-07-20 20:14:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lonni J Friedman 2009-07-08 20:35:37 UTC

Description of problem:
Since upgrading from F10 to F11, thunderbird now crashes randomly with the error:
INTERNAL ERROR on Browser End: Could not get the JVM manager

Version-Release number of selected component (if applicable):
3.0-2.3.beta2

How reproducible:
100% of the time when attempting to view any email message.


Steps to Reproduce:
1.start thunderbird
2.either click on any email message, or attempt to view the addons, and it will spontaneously crash.
  
Actual results:
thunderbird crashes

Expected results:
no crash

Additional info:
After googling, I found that the workaround documented here actually resolves the problem for me:
http://forums.mozillazine.org/viewtopic.php?f=31&t=50237&start=0&st=0&sk=t&sd=a

Comment 1 Lonni J Friedman 2009-07-14 20:55:49 UTC

One thing I should note/add is that with the workaround noted above, I can't access or use any extensions, themes or plugins.  I just get a blank, broken window where those modules should normally be accessible.

Comment 2 Matěj Cepl 2009-07-20 16:14:18 UTC

Yeah, you just removed all your extensions. Running with -safe-mode would give you exactly the same, I guess, except it would be reversible. Moreover, this is effectively the same as bug 510377, except I guess the problem is in xulrunner (which is foundation of both).

*** This bug has been marked as a duplicate of bug 510377 ***

Comment 3 Lonni J Friedman 2009-07-20 16:27:21 UTC

Sorry to burst your bubble, but this still reproduces if I undo the workaround, and start with -safe-mode

Comment 4 Matěj Cepl 2009-07-20 20:14:03 UTC

(In reply to comment #3)
> Sorry to burst your bubble, but this still reproduces if I undo the workaround,
> and start with -safe-mode  

Which means absolutely nothing for this bug to be closed as duplicate. Please, do not reopen it.

*** This bug has been marked as a duplicate of bug 510377 ***