SearchTempest.com

Over the last 2 weeks, I've been getting the "Retrieving Results From Google" message again when doing the following search (full search, all 416 cities, Sale/Wanted, All Sale/Wanted). Before 2 weeks ago, this search would properly load the cities in batches (waiting the 25 seconds per batch).

http://www.searchtempest.com/search?loc ... axYear=max

I tried doing the same search from a different IP address and it processed like normal for awhile before stopping after about 8-10 iterations of the 25 second search delay.

Thoughts?

Thanks for your help =)

We've had a handful of people report this, but unfortunately haven't been able to reproduce the problem ourselves yet. We're going to have a developer look into it in detail this week, and may write back with questions once we know more. Thanks for your patience!

Thanks =)

One question: if you scroll up to the top of the page after it gets stuck, is there a yellow notice box (below the search bar and above the first city) that explains you've probably hit the 5 minute delay from Google? It should appear 25 seconds after the cities get stuck 'retrieving results'.

No, there is not one of those boxes. It seems to me like it searches the first few cities closest to me (and they then disappear because there are no search results), but then doesn't search any other cities. The first city that it stalls on is Beaumont, TX (~136mi), so it's possible that it makes it all the way through the first batch of 25 cities, but I would guess that Beaumont would be in the top 25 closest cities, so it's possible that it's stalling before the first batch of 25 is finished.

I also tried changing the zip code to a California zip code and got the same result. It seems to process all or part of the first batch of 25 cities and then stalls.

I then tried it in Chrome, and boom, everything worked as expected! So it looks like the problem is with Firefox 50.0 (I'm using Windows 7 Professional).

Thanks for the added info. In the results 'preferences' section, have you increased the number of 'Results per city page' by any chance? The default is 20.

I'm also wondering if you could check for any javascript errors. To do that, go to the searchtempest homepage, and press CTRL-SHIFT-J in Firefox. That should open a console window (or pane). At the top-left will be a little trash can, which you can click to clear out anything that's in there. Then run your search. A bunch of new stuff should appear in the window. Leave it open until the freeze happens. If you could then copy anything that appears and send it to us in an email, (nathan at searchtempest.com) it would be very helpful.

Thanks!

URL: http://www.searchtempest.com/search?loc ... axYear=max

Cities per page: 50
Results Cities per page: 100

Not including Ebay, not including Amazon, Not including Oodle
Hide Expired Posts = No

Javascript Errors:
Use of getAttributeNode() is deprecated. Use getAttribute() instead. 6e41b3d-cf15a61.js:503:54
The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it. to.html
TypeError: this is null[Learn More] prebid.min.js:4:5337
TypeError: $(...) is null[Learn More] 30cf79b-9b1e94a.js:260:73
TypeError: $(...) is null[Learn More] 30cf79b-9b1e94a.js:262:2318
TypeError: $(...) is null[Learn More] 30cf79b-9b1e94a.js:262:2318
‘mozHidden’ and ‘mozVisibilityState’ are deprecated. Please use the unprefixed ‘hidden’ and ‘visibilityState’ instead. pubads_impl_105.js:49:288
‘mozHidden’ and ‘mozVisibilityState’ are deprecated. Please use the unprefixed ‘hidden’ and ‘visibilityState’ instead. container.html:16:1040
‘mozHidden’ and ‘mozVisibilityState’ are deprecated. Please use the unprefixed ‘hidden’ and ‘visibilityState’ instead. ad:1:5379
‘mozHidden’ and ‘mozVisibilityState’ are deprecated. Please use the unprefixed ‘hidden’ and ‘visibilityState’ instead. ad:1:5374
‘mozHidden’ and ‘mozVisibilityState’ are deprecated. Please use the unprefixed ‘hidden’ and ‘visibilityState’ instead. ad:1:5381
An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimi ... ve_Parsing container.html:16
An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimi ... ve_Parsing container.html:16
An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimi ... ve_Parsing container.html:16
An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimi ... ve_Parsing container.html:16


Hope that helps, thanks!

Oops, I forgot to expand several of the Javascript Errors:

Use of getAttributeNode() is deprecated. Use getAttribute() instead. 6e41b3d-cf15a61.js:503:54
The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it. to.html
TypeError: this is null[Learn More] prebid.min.js:4:5337
n http://ap.lijit.com/www/headerauction/p ... .js:4:5337
.bind/< http://static.searchtempest.com/www/js/ ... .js:119:53
t.createBid http://ap.lijit.com/www/headerauction/p ... .js:4:5558
c/pbjs.sovrnResponse/< http://ap.lijit.com/www/headerauction/p ... js:5:10808
forEach self-hosted
c/pbjs.sovrnResponse http://ap.lijit.com/www/headerauction/p ... js:5:10475
<anonymous> http://ap.lijit.com/rtb/bid:1:1
TypeError: $(...) is null[Learn More] 30cf79b-9b1e94a.js:260:73
GoogleDelayNotifier.showMsg http://static.searchtempest.com/www/js/ ... .js:260:73
CityGroup<.load http://static.searchtempest.com/www/js/ ... .js:229:87
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
StackedResults<.organizeGroup http://static.searchtempest.com/www/js/ ... .js:224:65
StackedCity<.close http://static.searchtempest.com/www/js/ ... js:280:312
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
StackedCity<.autoClose http://static.searchtempest.com/www/js/ ... s:279:2606
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
GooSeparate<.handleLoadingError http://static.searchtempest.com/www/js/ ... js:264:565
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
GooResults<.gooSearchRan http://static.searchtempest.com/www/js/ ... js:244:830
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
<anonymous> https://www.googleapis.com/customsearch/v1element:2:1
TypeError: $(...) is null[Learn More] 30cf79b-9b1e94a.js:262:2318
GoogleDelayNotifier.stopCountDown http://static.searchtempest.com/www/js/ ... s:262:2318
GoogleDelayNotifier.hideMsg http://static.searchtempest.com/www/js/ ... js:253:369
GoogleDelayNotifier.showMsg http://static.searchtempest.com/www/js/ ... .js:254:29
CityGroup<.load http://static.searchtempest.com/www/js/ ... .js:229:87
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
StackedResults<.organizeGroup http://static.searchtempest.com/www/js/ ... .js:224:65
StackedCity<.close http://static.searchtempest.com/www/js/ ... js:280:312
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
StackedCity<.autoClose http://static.searchtempest.com/www/js/ ... s:279:2606
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
GooSeparate<.handleLoadingError http://static.searchtempest.com/www/js/ ... js:264:565
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
GooResults<.gooSearchRan http://static.searchtempest.com/www/js/ ... js:244:830
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
<anonymous> https://www.googleapis.com/customsearch/v1element:2:1
TypeError: $(...) is null[Learn More] 30cf79b-9b1e94a.js:262:2318
GoogleDelayNotifier.stopCountDown http://static.searchtempest.com/www/js/ ... s:262:2318
GoogleDelayNotifier.hideMsg http://static.searchtempest.com/www/js/ ... js:253:369
GoogleDelayNotifier.showMsg http://static.searchtempest.com/www/js/ ... .js:254:29
CityGroup<.load http://static.searchtempest.com/www/js/ ... .js:229:87
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
StackedResults<.organizeGroup http://static.searchtempest.com/www/js/ ... .js:224:65
StackedCity<.close http://static.searchtempest.com/www/js/ ... js:280:312
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
StackedCity<.autoClose http://static.searchtempest.com/www/js/ ... s:279:2606
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
GooSeparate<.handleLoadingError http://static.searchtempest.com/www/js/ ... js:264:565
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
GooResults<.gooSearchRan http://static.searchtempest.com/www/js/ ... js:244:830
n/n< http://static.searchtempest.com/www/js/ ... 1.js:196:7
<anonymous> https://www.googleapis.com/customsearch/v1element:2:1
‘mozHidden’ and ‘mozVisibilityState’ are deprecated. Please use the unprefixed ‘hidden’ and ‘visibilityState’ instead. pubads_impl_105.js:49:288
‘mozHidden’ and ‘mozVisibilityState’ are deprecated. Please use the unprefixed ‘hidden’ and ‘visibilityState’ instead. container.html:16:1040
‘mozHidden’ and ‘mozVisibilityState’ are deprecated. Please use the unprefixed ‘hidden’ and ‘visibilityState’ instead. ad:1:5379
‘mozHidden’ and ‘mozVisibilityState’ are deprecated. Please use the unprefixed ‘hidden’ and ‘visibilityState’ instead. ad:1:5374
‘mozHidden’ and ‘mozVisibilityState’ are deprecated. Please use the unprefixed ‘hidden’ and ‘visibilityState’ instead. ad:1:5381
An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimi ... ve_Parsing container.html:16
An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimi ... ve_Parsing container.html:16
An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimi ... ve_Parsing container.html:16
An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimi ... ve_Parsing container.html:16

O_o

Thanks for sending that. Will take a look.

Everything is fixed and working again in Firefox 50. Thanks!