if the field is used like that then you will have

• 100,000 function calls to JHtml::_('select.option', ...

so 128 MBytes of memory being exhausted is expected

// Build the options array.
for ($i = $first; $i <= $last; $i += $step)
{
    $options[] = JHtml::_('select.option', $i);
}

• then IF execution succeeds we get size of the produced HTML to be about 3.5 - 3.6 MBytes, which is again not good

i think the field was never intended to be used like this, best policy is to disallow such usage,

1. Use '<select>'** for a sane limit of last - first < 1000
2. do not use function call ... JHtml::_('
3. if more than 1000 (or if some flag is set) then change display to be '<input />'

then also introduce a new JS validation type "integer"

<input ... class="validate-integer" data-first="0"  data-last="99999" />

Finally probably it is time that Joomla added an input validation masking JS library, i am sure this will be added eventually, it is just being delayed

Also another option is to use HTML5 form validation options
but currently joomla makes it hard to use this

Still, i think, adding an input validation masking JS library is best choice

I am going to close this as no one would ever be creating an integer field like that