Closed
Bug 860228
Opened 13 years ago
Closed 13 years ago
Uncaught crashes in xul.dll with flash 11.7
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: cumdacon, Unassigned)
Details
(Keywords: crash, stackwanted)
User Agent: Mozilla/5.0 (Windows NT 6.0; rv:20.0) Gecko/20100101 Firefox/20.0
Build ID: 20130326150557
Steps to reproduce:
I closed FF after using flash player 11.7 with sandbox on and acceleration on (it is compulsory these settings for me).
Addon: ADBplus, noscript, wot.
Safe mode too.
Actual results:
While with 11.5, 11.6 I become only "minidumps" in the folder every time I closed Firefox 18, 19, starting with flash 11.7 from released yesterday I become xul.exe crash every every every time I close FF, the new thing: even if I close FF after a very short time usage!! (In the past only when I used FF for a long time). Also more problem with the new flashplayer "sandbox enhacements" (changelog), but the problem was known since a long time!
Expected results:
Using flashplayer 11.7 with FF20 with acceleration on and sandbox on, I should not see minidumps but the main thing: I would never see this message from Vista sp2
A silent crash, signalized by the OS, the about:crashes is empty!
I already attached a dxdiag.txt.
Nome evento problema: APPCRASH
Nome applicazione: firefox.exe
Versione applicazione: 20.0.0.4833
Timestamp applicazione: 5152542c
Nome modulo con errori: xul.dll
Versione modulo con errori: 20.0.0.4833
Timestamp modulo con errori: 51525346
Codice eccezione: c0000005
Offset eccezione: 000973d8
Versione SO: 6.0.6002.2.2.0.768.3
ID impostazioni locali: 1040
Informazioni aggiuntive 1: 40d4
Ulteriori informazioni 2: 4062ad41ec8067256aa4c5e2b56d3c79
Ulteriori informazioni 3: 40d4
Ulteriori informazioni 4: 4062ad41ec8067256aa4c5e2b56d3c79
reprodubible (for me, I guess not for you) using a simple youtube video. and closing firefox.
Comment 2•13 years ago
|
||
As the crash is easily reproducible for you, can you get a stack trace (see https://developer.mozilla.org/docs/How_to_get_a_stacktrace_with_WinDbg)?
Flags: needinfo?(cumdacon)
Keywords: crash,
stackwanted
Updated•13 years ago
|
Summary: XUL.EXE silent crash more frequest with flash 11.7 → Uncaught crashes in xul.dll with flash 11.7
the stacktrace is too hard for my knowledge :(
Flags: needinfo?(cumdacon)
may you want to add Jeromie in the cc list for this bug? because this crash is discussed on the adobe forum too, since 1 year ago...
the bad is that with 11.7 the frequency of the issue is bigger than in the past.
surely related to changlog "sandbox enhacements".
Comment 6•13 years ago
|
||
(In reply to candaules from comment #3)
> the stacktrace is too hard for my knowledge :(
If you'd still be willing to try, you have just to follow the steps in the wiki up to, and including, the section titled "After the crash or hang". The necessary commands can just be copy-pasted :)
(In reply to candaules from comment #4)
> may you want to add Jeromie in the cc list for this bug? because this crash
> is discussed on the adobe forum too, since 1 year ago...
Do you have a link to the thread or an adobe issue number?
The problem is that without being able to reproduce it or having actual crash information we can't really tell what kind of problem this.
yes you are right.
it is hard. in the task manager the 2 flash processes close itself ok. but firefox.exe dont closes itself. then this message with xul.exe.
sandbox off = no issues.
here an example
http://forums.adobe.com/message/4777482
http://forums.adobe.com/message/5122648 (mixed content)
thanks.
Comment 8•13 years ago
|
||
I don't see any information in those 2 threads that could get us further.
Closing as incomplete for now as we don't have enough to act on, please re-open or comment here if you:
* find steps to reproduce this on other machines or
* manage to get a stacktrace
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Updated•4 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•