Well, it has to be environmental I suppose, rather than a hard bug in
Flex. Have you reported it to Adobe and/or Mozilla ?
Tom
On 29/01/16 12:05, Maxim Solodovnik wrote:
here is one on the latest reports:
https://crash-stats.mozilla.com/report/index/23831f11-4d71-4964-b8d5-595622160128
It seems nothing was done regarding it :(
On Fri, Jan 29, 2016 at 4:45 PM, Tom Chiverton <t...@extravision.com> wrote:
If you visit
about:crashes
then you can click through to the processed version on Mozilla's site,
which will have already looked at it and decided if it is a known issue or
not.
Tom
On 29/01/16 09:49, Maxim Solodovnik wrote:
then examine it using winedbg (found no other way)
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
