Does it happen on both the compressed and uncompressed versions? Can you try the older 1.7 pre-release versions so we can narrow down where the problem lies?

http://code.jquery.com/jquery-1.7b1.js

http://code.jquery.com/jquery-1.7b2.js

I was testing a compressed 1.7rc1 version

-jquery-1.7b1.js (uncompressed) crashes

-jquery-1.7b2.js (uncompressed) crashes

-jquery-1.6.4.min.js (compressed) works

I will try to comment out code to see where it crashes

I have no clue why it is crashing but if you comment out line 1635:

supports.supportsFixedPosition = (inner.offsetTop === 20 || inner.offsetTop === 15);

we no longer crash. Does this make any sense?

Wow, thanks for digging into this! I suspect it's a duplicate of #10613 which crashes IE8 about five lines above that. Can you try a test where you include jQuery at the bottom of the page, just before the end of the body? If that works then I think we are dealing with the same problem.

no prob, I was already set up for it and what a great way to spend a Friday night ;)

but it still crashes if I put it before the end </body>

Mike, does the 1.7 final still crash the simulator? We haven't given up and will be doing some other changes to 1.7.1 in the support.js area but this didn't seem critical enough to prevent the release.

Still happens in 1.7, I (and anyone else building PhoneGap apps for BlackBerry) will have to stick with 1.6.4 until this is fixes because there is no workaround that I am aware of.

Not a big deal for me because I do not need any of the new features in 1.7 but I would like to eventually upgrade.

The difference is that the fixed position tests aren't run at all on pageload in 1.6.4. @mike: perhaps if you try to run http://api.jquery.com/offset in 1.6.4, you'll get the same error when it tries to determine fixed position support? I would test, but lack a bb.

Calling:

$(window).offset();

in 1.6.4 does not crash the app

Mike, does this still occur? We don't have a simple way to reproduce so that makes it hard for us to fix as well.

Yes, it still happens; BlackBerry simulator still crashes with 1.7.1 but not with 1.6.4.

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

Replying to [comment:2 anonymous]:

I was testing a compressed 1.7rc1 version -jquery-1.7b1.js (uncompressed) crashes -jquery-1.7b2.js (uncompressed) crashes -jquery-1.6.4.min.js (compressed) works

I have the same problem. By using jquery.1.6.4.min.js still happening. What is the solution to test in the simulator under these conditions?

Does the 1.8b2 release work?

What platform are you running the simulator on?

Replying to [comment:17 dmethvin]:

Does the 1.8b2 release work? What platform are you running the simulator on?

Sorry, the version 1.6.4 if it works, but stops working in conjunction with mobile jquery 1.1.0 in the SDK simulator WebWorks.

I know it's been a while, but I'm just checking to see if later versions work here. Or perhaps RIM updated their software? Nobody else has reported this and we don't have a way to diagnose it, so I'm inclined to close.

We also ran into the same problem. Just including the JQuery js (compressed or uncompressed of ver 1.7.2) was causing the BB Simulator (os 7) to crash.

Do we have any solution to this yet? Is this solved in 1.8?

This is really preventing us from having a hybrid app using JQuery on BlackBerry. Please help.

Commenting line below (line 1636) as recommended above solves the problem

offsetSupport.fixedPosition = ( inner.offsetTop === 20 || inner.offsetTop === 15 );

Okay, not sure if we can fix this but at least we have a repro and a suspect.

Is this still a problem? Can someone who was affected test with jquery-1.9b1.js and see if it's still an issue?

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!