Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

ఇంకా తెలుసుకోండి

flash hang since a lot years. bugzilla is sleeping?

  • 52 ప్రత్యుత్తరాలు
  • 8 ఈ సమస్యలు కలిగి ఉన్నాయి
  • 2 వీక్షణలు
  • చివరి సమాధానమిచ్చినది anuswara

more options

https://bugzilla.mozilla.org/show_bug.cgi?id=789379

reopened 2012 https://bugzilla.mozilla.org/show_bug.cgi?id=788423 now 2015 ?? I am without words. therefore I ask if Bugzilla is spleeping.

https://bugzilla.mozilla.org/show_bug.cgi?id=789379 reopened 2012 https://bugzilla.mozilla.org/show_bug.cgi?id=788423 now 2015 ?? I am without words. therefore I ask if Bugzilla is spleeping.

న anuswara చే మార్చబడినది

ప్రత్యుత్తరాలన్నీ (12)

more options

thanks! I write here a reply: questions/1050362

more options

ok friends, after one week without issues.... ......again!! lets go! https://crash-stats.mozilla.com/report/index/76f23242-8fca-4efb-9e2b-6ad642150316

(driver 347.52)

switching to this tab https://www.facebook.com/pages/Rocio-Mu%C3%B1oz-Morales/312768552095060?fref=ts

న anuswara చే మార్చబడినది

more options

its strange because I have this setting (suggested by Liu from adobe bugbase one year ago): dom.ipc.plugins.timeoutSecs to -1

more options

న anuswara చే మార్చబడినది

more options

We get from Firefox always the same sugestions: update drivers, update flash, etc.

I have also problem with FF crashes and crash is only in FF, Chrome with the same drivers and the same flas worklike charm.

So this time instead i get sugestion a will give you one:

Roll back firefox to version 33 or 34 where all work or look what you add after 34 version to see where you make mistake.

A lot of people like to use firefox but what you do with FF after version 30 is ridiculous, you force us to like things that you like and you make more and more bugs after version 34.

I think that if you continue with this kind of work all user will uninstall firefox and install chrome, opera or some other browser, becouse a 10 to 25 crashes every day when closing firefox is too much to use this browser.

more options

ok, in my case updating did not help. what told me nvidia? try re-installing firefox. I guess that we never find a solution. mozilla "aks to nvidia", nvidia "ask to mozilla", and the user what should do? I hope with bugzilla, but I serioulsy doubt.

yes blackwolfy, only with FF I notice this issue.

yes 34 is good! but now with a lot of security risks and at the moment I dont want to switch to "entreprise" solution (for normal user too, ok).

I understand the bug "flash hangs without specific steps to reproduce" from 2012 until today (until when?), then I had "hang swf.dll" but Campbell confirmed that it has been fized with flash 17. Also Adobe is worked well. I never had this kind of hang with swf. So I warmly hope (but I doubt) that this shutdownhang where nvidia driver is quoted (in the crash report) will be fixed, but look please at the reply from nvidia:

From the problem description, I understand that you are having issues with Firefox browser.

Sorry to hear that, in order to troubleshoot the issue could you please make sure that the FireFox version is updated and also if possible uninstall and reinstall the browser.

second reply:

Since the graphic card is always drawing to your screen, any application/program/browser crashes it will give you the error about the display which does not necessarily related to the Graphic card always. It could be an unstable Firefox version. In order to further narrow down the issue, please make sure your windows is updated and also Java is updated.

then I replied: my windows is up to date, I dont have Java on my pc, is 36.0.4 an unstable version?

yes friend, I guess that now Firefox is for expert users only.

or I should read an official statement from mozilla:

"starting from FF36, users with an old GPU (end 2012) have to refuse to H/W acceleration in firefox (even if DXVA works fine with 4K 30p) and buy a gtx980 ;)

edit: ahahaha did you read what I wrote here just now? ahahaha after posting I received the third reply from nvidia:

I would suggest you to check with firefox also once to confirm if there is any kind of compatibility issue with the graphic card.

therefore: Mozilla, there is any kind of compatibility issue with gtx650? thanks.

న anuswara చే మార్చబడినది

more options
more options

న anuswara చే మార్చబడినది

more options

https://crash-stats.mozilla.com/report/index/624a3131-3ffc-4ccf-b6d6-5c60b2150415

doing nothing since I was at dinner. I filed a bug but Mr. engineer Smedberg dont want to spend time.

Congratulations to Mr. Engineer Sme(r)dberg, very professional!!!!!!!!!!!!!!!!!!!!!

న anuswara చే మార్చబడినది

more options

It is essential that there are reliable steps to reproduce (STR) the issue to makes it possible for a developer to replicate the problem and track down what is causing this. That wasn't the case in that bug, so the bug was closed as RESOLVED INCOMPLETE like always happens in such a case. Is case where a plugin (Flash Action script) is involved it is even more difficult to investigate what happens.

more options

If I was absent when the crash occurred, what should I do? again: is the crash report not useful? if it isnt, why it exist? to what purpose mozilla dev released a crash report?

I hope that Campbell will be able to understand.

surely it does NOT happen when I watch youtube videos. If i would know all the steps, I were a (brave) engineer ;)

Anyway I wrote to: mozilla, bugzilla, abobe bugbase, campbell. we will see if they will close my bug hurriedly as Smedberg did after 3 seconds.

Anyway look please at my other bug: it has been accepted, a crash report was enough, without steps to reproduce. I think that it depends from dev. : a not brave dev want the steps to reproduce, a brave dev accepts the bug, as you see.

Another dev (regarding the fix introduced in ff36: unwanted logout from Fb and YT) told me: ok I accept the bug because I am interested too in restoring the old behaviour. And if this dev were not interested? is this a professional behaviour? (volunteers should be professional too i.e even without money). I use it too therefore I resolve the bug. I dont use it therefore I dont resolved the bug.

Anyway , as you see, we talk talk talk (not only in this topic), we write write write, we send reports reports...but solutions? perhaps philosophy is more concrete than binaries ;)

OT: perhaps the only professional dev are people from MPC-HC: it seems that they have a need to resolve, to make amelioraments, if I dont reply for a while they contact me again, after a month they want to resolve, very impressive, perhaps they have more time or they deeply love their programm..on the other hand we find videolan: a topic = a nuisance for them, instead of an exciting adventure. /OT

In other words: the user should be drived by dev (or by representatives), the dev should say "try this, ...then try this, ok now send me a dxdiag so I can look better on your OS...the crash refers to DLL, I send this one and replace yours..." instead SOME dev wait that the user solve the issues. The report should help them (utopie). Do you remember with ff11?? the reply: try with ff12 since the report has been improved; then ff26: please try with ff27 because we intrduced a more detailed crash report....and so on, so on, so on. Therefore exist forums. If all the issues were reproducible simply "click here and you will get a crash", this were wonderful, but not realistic.

I guess that the difference between an engineer and a good engineer is intuition (if you want: a bit phantasy even handling with arithmetics). Engineer is not exactly an accountant. Of course he is deeply related to arithmetics and arithmetics and binaries are not a matter of opinion, but without intuition its hard to become a good engineer (or a physic ). A "squared" engineer is a bureaucrat.

న anuswara చే మార్చబడినది

more options

Much better the reply of another dev (not Smedberg): "Blame the buggy Flash plugin and report it to Adobe."

  1. 1
  2. 2
  3. 3