502059 - The procedure entry point JS_GetOperationLimit could not be located in the dynamic link library js3250.dll

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Bart S]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; InfoPath.1; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Build Identifier: 3.5 through upgrade option in the menu of ff3.0.11. Unable to get details

Updated 3.0.11 with the check for updates option in the About menu.

After download/install/restart FF the error comes up
"The procedure entry point JS_GetOperationLimit could not be located in the dynamic link library js3250.dll"

Starting FF3.5 in safe mode gives the same error before any option to disable add-ons etc.

Unable to retreive exact version information. But from the exe properties:
File version: 1.9.1.3462
Build ID: 20090624013405
Product version: 3.5


Reproducible: Always

Steps to Reproduce:
1. Run FF3.0.11
2. Update to 3.5 using About menu check for updates
3. Start FF3.5
4. Get the mentioned error
5. Start FF3.5 in safe mode
6. Get the mentioned error


Expected Results:  
Any check for updates option installing new updates MUST have a running program.
According to the other bug reports this js3250.dll seems extremely buggy. In such case do not release it !!

Comment 1

[Matthias Versen [:Matti]]

>The procedure entry point JS_GetOperationLimit could not be located in the
>dynamic link library js3250.dll

This is a sign for either a failed update or some old dlls in your application Directory.
Please reinstall Firefox in a complete empty directory (uninstall Firefox, delete the Firefox folder under c:\program files\ and install FF3.5 again)

>According to the other bug reports this js3250.dll seems extremely buggy. In
>such case do not release it !!

Sorry but this statement is incorrect. This bug report is an installer bug and not the fault of the Javascript dll and you are the first one with this issue and we have a few million installations.

Comment 2

[Bart S]

Hi Matti,

Thanks for replying. 

No any message showed that the update failed... actually it looked to run perfect. If it is older dll's in the FF folder, isn't that a task of the installer ? even if a file is locked, it should at least prompt that something is wrong, not show everything fine and when you try to startup FF getting an error.

Certainly I am not the only one having this problem. Please refer to http://support.mozilla.com/tiki-view_forum_thread.php?locale=fi&forumId=1&comments_parentId=378535 for more of the same error reports. Probably I am the first one report it into bugzilla. 

Doing a search on js3250 in bugzilla gives 197 bugs which is quite a list especially if you see that say more than 50% of these bugs are critical.

Anyway I will try to do a clean intall. Any hints how to keep my FF3.0.11 settings, history and bookmarks etc ?

Comment 3

[Matthias Versen [:Matti]]

>Doing a search on js3250 in bugzilla gives 197 bugs which is quite a list
>especially if you see that say more than 50% of these bugs are critical.

js3250 is the Javascript Engine and 197 found bugs is not many after all this year.

This can be also caused by an extension which contains binary components.
Did you override/disabled the addon compatibility check ?
Does it happen in the safemode ?
http://support.mozilla.com/en-US/kb/Safe+Mode

Do you have a Zonealarm addon installed ?

Comment 4

[Bart S]

I am not going to twist about 197 is a lot or not... that's relative ;o)

After the update, I could not start FF either in normal or safe mode. The dialog with the error message comes. In safe mode the error dialog shows up --before-- the dialog to disable all add-ons. As the dialog to disable add-ons does not show before the error, it looks to me that there is a glitch in FF that has nothing to do with the add-ons.

No zone-alarm addon installed, nor is zone-alarm itself.

Comment 5

[Matthias Versen [:Matti]]

Did you try the clean install (in an really empty directory) ?
The error message means that some stupid DLL wants to call an interface in JS3250.dll which got removed with FF3.5 (no, that is no bug !).

Can you try to create an additional test profile ?
http://kb.mozillazine.org/Profile_Manager

Comment 6

[Bart S]

written from Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1) Gecko/20090624 Firefox/3.5 (.NET CLR 3.5.30729)

Disabled all add-ons in 3.0.11, uninstalled some Apple Theme from which I did not know it was there (probably tried it once) but the theme was not in use. The update mentioned the incompatibility of the theme, and that it would be disabled. First time I pressed ok for it, second time I uninstalled it.

Used the update function again and its able to update to 3.5.
After updating it mentions there are two plugins incompatible and they are disabled.

One by one enabled the add-ons again in FF3.5 and it still works.

Either the theme, or one of the 4 plugins cause this problem when they are respectively installed but not used (theme) or enabled (add-on)

The exact name of the Apple plugin I not have anymore,
The addons disabled before update and enabled after update are:
- NoScript 1.9.5
- Image Zoom 0.3.1
- Greasemonkey 0.8.20090123.1
- Adblock Plus 1.0.2

Question: In safe mode, will a theme, or add on be called before (!) the prompt to disable all add ons ?

Comment 7

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.

Comment 8

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.