jit compiler causing crash

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
5 years ago
5 years ago

People

(Reporter: samkarora, Unassigned)

Tracking

24 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Created attachment 818096 [details]
crashreport.JPG

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release)
Build ID: 20130910160258

Steps to reproduce:

I click on a link, where javascript will load 10 different maps at the same time. Javascript gets the json object from server and then zingchart JS library will produce the maps from those json objects. 


Actual results:

Firefox crashed. I tried in safe mode it worked. In normal mode, when I disabled everything, it was still crashing. Then I disabled JIT compilers in normal mode it worked. On checking the crash report, it generated something about jit compiler


Expected results:

It should produce maps or load the page without any crash. 
CRASH REPORT ID: ID: a965af5c-553e-4658-9f83-e50c22131016
(Reporter)

Comment 1

5 years ago
Also, when I remove firefox V24 and installed V22, it worked file without disabling JIT compilers.

Comment 2

5 years ago
Hi Chirag,

Would you please provide the link with which you have checked the above scenario so that we could check  

the issue solved in latest aurora builds, currently FF 27.0a1 ?

Whiteboard: [bugday - 20131021]
(Reporter)

Comment 3

5 years ago
I have the website on my localhost and on intranet. Its not available online, but whenever I use the latest FF version FF crashes due to JIT. When I used the previous version V22 it worked fine. If you want any of the team member could use team viewer to access the intranet and check the bug.
Is this still an Issue?
If yes, also testing against Nightly?

http://nightly.mozilla.org/
Flags: needinfo?(samkarora)
resolving per above.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Flags: needinfo?(samkarora)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.