Opened 15 years ago

Closed 15 years ago

#1803 closed bug (fixed)

Double clicking legend in wms layer name does not show property dialog and make the whole system crash

Reported by: gcontreras Owned by: mhugent
Priority: critical: causes crash or data corruption Milestone: Version 1.2.0
Component: WMS Version: Trunk
Keywords: Cc:
Must Fix for Release: Yes Platform: All
Platform Version: Awaiting user input: no

Description

I loaded a wms layer in qgis version 1.1 and in a self compiled from trunk and did a double clic in the wms layer name in legend, the properties dialog wasn't shown and qgis started to consume a lot of memory until it makes the whole system unstable and crash. I also tested with a debug version and it works correctly.

Change History (7)

comment:1 by lutra, 15 years ago

Hi,

can you please a post a URL that can be used to test and try reproduce the error?

comment:2 by gcontreras, 15 years ago

Hi,

I've been using this two wms servers

Also I traced the problem to a connect statement QgsLegend::legendLayerShowProperties().

this is the line (around line 733)

connect( rlp, SIGNAL( refreshLegend( QString, bool ) ), this, SLOT( refreshLayerSymbology( QString, bool ) ) );

comment:3 by gcontreras, 15 years ago

just putting any statement after the connect statement fixes the problem, I put the following line:

QString fix="quick fix";

and now is working.

comment:4 by lutra, 15 years ago

Type: bugpatch

Can this be considered a patch?

comment:5 by gcontreras, 15 years ago

No, I will do some more testing to try to find why the raster properties dialog for wms is very slow and why the connect statement hangs with wms but not with raster. did you reproduce the error?

in reply to:  5 comment:6 by lutra, 15 years ago

Platform: WindowsAll
Type: patchbug

Replying to gcontreras:

did you reproduce the error?

yes, I did make to reproduce the error on qgis 1.2 on linux.

comment:7 by mhugent, 15 years ago

Resolution: fixed
Status: newclosed

I think r11201 fixes this issue. Please reopen this bug if it isn't.

Note: See TracTickets for help on using tickets.