GWT 2.5.1 DevMode - Unexpected module reload with Firefox

[Arnaud Brochard]

Hi folks,

I just updated my company's application to GWT 2.5.1 and noticed an unexpected behavior with Firefox, not present in 2.4.0. On each URL #token change (either manually in the navigator address bar, or via the Window.Location.assign method), I noticed that the GWT module is fully reloaded (in Firebug, the <module>.cache.js file is instantiated again). This is not the case with Chrome, or Firefox with GWT 2.4.0.

As the application is quite large and slow to instantiate in devmode, I would like to fix this behavior (either in my code if I did something bad, or in GWT is this was added in 2.5.X). I tried to debug the bootstrap javascript, set a bunch of breakpoints anywhere (any code that can clear the document contents, or history change, such as location.reload, window.onunload, the history events, etc.), but I can't find anything

So I got no clue right now. Do you know of any changes between 2.4.0 and 2.5.1 which could trigger this behavior ?