Subversion Repositories SmartDukaan

Last modification

• Rev 37673 2026-09-17 13:13:07
• Author: amit

• Log message:

  Hold the browser lane around the oppo/realme/motorola drivers
  
  Takes BrowserLane (common r37672) before new ChromeDriver and releases it after
  quit() returns -- the 850MB is resident for the whole chunk, not just at
  startup, so bracketing only the constructor would protect nothing.
  
  Five minutes of waiting, then give up and return what we have: the only things
  that can hold the lane that long are the other brand mid-chunk or the knowlarity
  scrape in the fofo tomcat, and giving up costs nothing because an unstamped imei
  stays pending and the lane's next turn picks it up.
  
  CheckMotorolaWarrantyTask carries a comment saying 'do not let this job overlap
  the oppo/realme window' that nothing ever enforced. It is wired here too so it is
  already safe whenever it gets a trigger -- it still has none today.
  
  Note on sizing, since the obvious knob is the wrong one: shrinking CHUNK from 25
  was evaluated and rejected. The idle window is a fixed 20s bolted onto a variable
  work period, so 25->10 moves the duty cycle only 96% -> 91% while costing 8.4%
  of daily throughput and 2.5x the driver launches. The lever for duty cycle is the
  fixedDelay gap, not the chunk size.